They're scriptable; they just can't take expressions.
We set most Saver clips by script upon creating the comp from our project management software. I also have a comp script that creates Savers for a particular template. Here are a few relevant lines from that script:
- Code: Select all
x,y = c.CurrentFrame.FlowView:GetPos(c.nullorig)
origsv = comp:AddTool("Saver", x+2, y+1)
origsv.Clip = origpath
origsv.CreateDir = 1
origsv.OpenEXRFormat.Depth = 1
origsv.Input = c.nullorig.Output
origsv:SetAttrs({TOOLS_Name = "origsaver"})
Line 3 sets the file name, and origpath (orig being short for 'original resolution') is created elsewhere in the script. You can get the composition's filename by querying its attributes:
- Code: Select all
dump(composition:GetAttrs())
That will display all of the comp's attributes. They're a sub-table under that method, so you can access the comp's name with
composition:GetAttrs().COMPS_Name
You'll probably want to do a little work to strip off the file extension.