Thanks, Chris. Your reply made me look at it again and I finally hit upon the answer… The node I wanted was several nodes up the tree and stuck in the middle of some single input nodes:
[value input.input.input1.input.input.name] I just have to find a way to logically make sense of the way this works, so I don't get confused again! ;^) Rich Rich Bobo Senior VFX Compositor Armstrong-White http://armstrong-white.com/ Email: [email protected] Mobile: (248) 840-2665 Web: http://richbobo.com/ “Many of the great achievements of the world were accomplished by tired and discouraged men who kept on working.” - Unknown On Oct 30, 2012, at 4:14 PM, chris <[email protected]> wrote: > On 10/30/12 at 8:43 PM, [email protected] (Rich Bobo) wrote: >> So, why isn't the second input called "input1"? What is >> its name? > > [value input1.name] seems to do the trick (at least on a merge or a switch > node) > > hth > ++ chris > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > 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
