New Nuke Multishot Compositing (aka Graph Variables)

Nuke 16 is out with a new addition to managing scripts.

Using script level variables to allow a single script to drive multiple shots and reduce need for copy paste.

Seems like a sensible addition for large scripts. Some folks have in the past used manual ways of creating switches, but now being integrated into the app overall makes this much better.

Has application beyond multi-switch. If you just want to make your re-grain or other compute heavy process controlled by a central toggle to speed up work, that’s a nice way of doing it.

4 Likes

Yeah this is it. Exactly what we’ve needed for a while now. Do we have a feature enhancement request yet?

4 Likes

I’m not seeing one

Partially it’s my reverse users group, but this is further reaching.

I pitched this to @fredwarren at a dinner a couple years back in Santa Monica but honestly I don’t think I did a good job of explaining it.

I dispute that you were unable to explain well - perhaps your doppelganger took that dinner?

1 Like

Have been using it since inception. Is great. Still behind Gaffer and Solaris, nicely expandable with NDK a Python. What will be interesting is if Nuke Studio implements this at the timeline level. Someone call Will Harris!

1 Like

Nah I was sitting at the next table over.

Aaron Paul What GIF by Breaking Bad

This is what I’m talking about…

Add a few custom toggles to your project settings.

Then in any field that can take an expression, you can reference these variables.

In this case, the standard ‘disable’ attribute (present in any Nuke node), here o on the blur node. Global enable/disable variable for any group of nodes in your script / node tree.

Bingo!

3 Likes