one idea for "pass management" that seems to work failrly well without a lot of overhead or customization is to just have a little backdrop area off to the side where you bring in CG renders, and then make clones of those reads from there to use in your script.
when a character or batch of CG is updated with a new version, you just select 'em all in your backdrop area and alt+up arrow to bump to the next version, and it updates throughout your script. gives you a nice one stop shop to update your CG. there's a snippet of code out there (nukepedia?) that will help bulletproof this - it will find and update to the latest version of something instead of just doing a +1 bump like the stock foundry versioner does. Useful if you get a TD who likes to skip versions and you know, render with gaps (v1, next one is v4, next one is v7, whatever) or if cg versions tend to get out of sync where you work. We have that script keybound to alt+shift+up I think. just one way of working, might give it a try. one thing - DO NOT DO CLONES FOR READS IF YOU ARE USING 6.3v7 or below or you'll get caught up in that nasty clone bug occasionally that breaks your script when you delete a clone and save. Use postage stamps instead, and hide the input. They fixed the clone bug for 6.3v8, so all good there. On Thu, Nov 1, 2012 at 4:32 PM, Nathan Rusch <[email protected]>wrote: > Hugo's idea might be the best solution if you're dealing with that many > Reads. That is, to remove any expressions from the Reads, and instead, use > a knobChanged callback on your master NoOp to actually change the paths on > the Reads when its parameters are changed. > > Expressions get evaluated a LOT, even when just moving viewer inputs > around, and string assembly expressions can be particularly heavy. > > If this doesn't sound like a workable solution, can you give some more > info on what specifically would require you to use expressions? > > -Nathan > > > -----Original Message----- From: Calle Granström > Sent: Wednesday, October 31, 2012 6:27 AM > To: Nuke user discussion > Subject: RE: [Nuke-users] Halt expressionlink? > > > So meen adding a knob to my read-nodes that reads a shot environment > variable to set the path..? From where should I store this variable? I want > it to be easy to update.. I guess not a Noop-node, what should I use? > > /C > > > -----Original Message----- > From: > nuke-users-bounces@support.**thefoundry.co.uk<[email protected]>[mailto: > nuke-users-bounces@**support.thefoundry.co.uk<[email protected]>] > On Behalf Of Martin Winkler > Sent: den 31 oktober 2012 13:41 > To: Nuke user discussion > Subject: Re: [Nuke-users] Halt expressionlink? > > We have a setup where all read-nodes get their filepath from one >> Noop-node. >> > > I'm intentionally ignoring the expression problem for now, but.. is there > anything wrong with using a shot environment variable to set the path? > Because that's what everybody does (or, seems to be doing at least). > > -- > Martin Winkler, Geschäftsführer > Grey Matter Visual Effects GmbH > Georg-Friedrich-Str.1 > 76530 Baden-Baden > Tel. 07221 972 95 31 > HRB 700934 Amtsgericht Mannheim > Ust-ID Nr.DE249482509 > ______________________________**_________________ > Nuke-users mailing list > [email protected].**co.uk<[email protected]>, > http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> > http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> > > ______________________________**_________________ > Nuke-users mailing list > [email protected].**co.uk<[email protected]>, > http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> > http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> > ______________________________**_________________ > Nuke-users mailing list > [email protected].**co.uk<[email protected]>, > http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> > http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> > >
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
