There is multiple solution to this. One would probably be the beforeRender callback where the write node would modify the path of the read node. You could also save a .py template with some placeholders and use the sys,argv to fill your placeholders. So you would always use the same .py file but depending of the argurment that you provide in the command line, Nuke would render to your desired location without saving a script
But I would start with the beforeRender callback. Just put a simple function that modify the path of the read. -- Hugo Léveillé On Thu, Feb 11, 2016, at 07:00, Thomas Volkmann wrote: > Hi, > > let's say I have a couple of sequences that shall all run through the same > nodesetup and then get written to a new location. > What is your typical setup for this? > At the moment we do it with linked switches, but if you want to send stuff to > the renderfarm, you have to save a scene for every switch setting. > > I was wondering if Nuke is aware of which write node is active, and have the > Read-node load the footage accordingly. > Basically: > if Write1: all [SHOT] tokens in all Read-filepaths get replaced with "sh001" > (you define that stuff in a text node, or it is the Write-name, or whatever) > if Write2: all [SHOT] tokens in all Read-filepaths get replaced with "sh002" > and so on... > (manually set a default while you are working and no write is active) > > Would that be possible somehow? (Maybe there is a much better solution that I > don't know about?) > > cheers, > Thomas > _________________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
