Hi folks, I am currently working on a show where I am setting up cameras and 3D background. Now I am getting to a point where I need to set up hundreds of shots and I can't see myself writing out file names for each of those every time.
I have already made my life easier by creating a script, where I have only a set of three write nodes which pump out all my set ups. A NoOp node is used to define the output directory and the file name. And a master switch lets me pipe through all the elements for each shot, where said switch drives another switch for my cameras (script is attached). The only thing that's missing is the ability to have some kind of way of also switching between names. I wouldn't mind a scenario where I write the name for each shot once but it gets piped into the write nodes. I'm not sure that this makes enough sense without looking at the sample script :) But this is basically how it goes: shot 01, 02, 03 are foreground elements and connected to a "master switch node" -> camera 01, 02, 03 go through a camera switch node (linked to master via expression) when shot 01 is turned on -> camera 01 follows, creates background by being piped into 3D scene -> shot 01 is keyed onto background (for reference) -> result is written to harddrive The ideal scenario would be the exact same but with the the name also controlled by a switch (or similar), so that when shot 01 is turned on the file name results in "shot01.tif", shot 02 results in "shot02.tif" and so on. Sorry for that massive post.
AutomatedNamingExample.nk
Description: Binary data
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
