- over 1,000 free tools for The Foundry's Nuke
fxT_cloneViaExpressions v1.3
This location is for Registered Users Only.
Perhaps you need to login or register.
12.2, 12.1, 12.0, 11.3, 11.2, 11.1, 11.0, 10.5, 10 or later
Linux, Mac, Windows
27 Feb 2022
241
fxT_cloneViaExpression
Clones are a nice feature in Nuke, but the random bug that comes with clones can corrupt your nuke-script. This python script lets you replace the clone feature in Nuke with a tool that automates the process using expressions. The difference is that you will have a parent and child node in stead of the non-directional functionallity of the clone feature.
Features:
- Remove the clone feature in the menu and replaces it using the same shortcuts (alt+k, and alt+Shift+k for declone)
- Only sets expressions on visible knobs (hidden knobs, and otherwise unsafe knobs to link will not be linked)
- Takes into account for multi and single knobs (color knobs), this will be restored to singleValue/original state when you declone the node.
- Links all selected nodes (you can select multiple nodes and link them at the same time)
- label will be set on the 'expressionCloned' node so you know where its coming from
- Won't let you link nodes that are considered unsafe to link (by class or name of node)
- also works for nodes with curve-knobs (such as Huecorrect, colorCorrect, Sampler, ect.)
Change Log:
v. 1.3: some PEP8 python standard fixes, remove global statements and genrally improve code. Fix some declonig isses with nodes that have curves so they reset properly.
v. 1.2: Minor bug fix.
v. 1.1:
- Fix text knobs links (now sets tcl value to parent nodes value)
- Now allows curveknobs to be linked. They can not be linked, so this is solved with a small callback (fully managed so it's not slow and don't
leave any callbacks behind if nodes are deleted or undone ect. Was sceptical to implementing this myself at first, but its written in a 100%
safe way. Reason I decided to implemement this was that sometime I want to link the ColorLookup node which was not possible by a simple link)
- removed user choice to decide if disable knob should be linked, I never used this so decided to remove it (want it back? I've included a
simple explination on how to change this in the code)
v. 1.0 : Firste release
Compatevility Info
Tested on nuke 11 and 12. Support for Nuke 13 in unknown atm, when I have acess to this version, I will update for compatebility if there are any changes needed for python3.
Comments
It's a great tools.
I clone a node and i "d" this node,the other node can't disable,too.
Can you replace this?
About the disable. That one was intentionally left out of the linking. The reason for this is that the linked node is often one you want to disable manually to see what it's doing, or the artist forgets that it's linked and when you manually disable it will set a keyframe on the node since it's linked. I wanted to keep it out of the linking process to allow for manual enabling and disabling without having keys set on the node.
If you want this to happen you can easily modify the python script, by removing 'disable' from the ignore_knobs list. Hope that helps
I will use it. Thank you.
Now, thanks for making clones great again! haha.
RSS feed for comments to this post