Teleporting a Read Node

| Category: Tip of the Week | | Comments (1) | Views: 36

PCB with testpads
Oh my!  Is this a Tip of the Week? No.. Well, I guess, it's a short one.. Ever wanted to access a read node or a stack of nodes from somewhere else in your massive script and you don't want it to look like a circuit board or spaghetti pile? Here's a nifty trick to put in your arsenal.

I'm assuming you're using Nuke as your compositing package. If you're not.. Well, uhm.. That could be a problem.  Anyway, grab a PostageStamp node.  Attach it to a dot or stack of nodes or simply a read node.

Under the PostageStamp options, click Hide Input and deselect the node. Goodness, now we can move that PostageStamp anywhere and it references that stack! But, wait, I don't know what it is, what the original file was, and let's say I do (I really do, all the time).

In the label section of the PostageStamp, enter the following:

[lindex [split [basename [value [topnode].file]] .] 0]

Now go ahead and quickly disable and enable the node. Look at that! Now we have a PostageStamp node that references the original Read, and on top of that, I can move it around and not get too cluttered. Wicked. Now all you have to worry about is updating only ONE read should be referenced by a bunch of other nodes. Keep it clean and neat people!

Bonus Points Awarded: Set up your Nuke menu.py to automatically set your PostageStamps to do this!
Enhanced by Zemanta

1 Comments

This one's nice... I saw a version of this using only dot nodes when working on one show, but the TCL you've added makes it usable in production. Had to take over one guy's shot who used this. Almost had a heart attack until I went through node by node and figured out what he'd done.
(My workaround was postage stamp and manually changing the Name of it. But the TCL is a nice touch


Leave a comment