- over 1,000 free tools for The Foundry's Nuke
default - automatic knobDefaults v5.0
This location is for Registered Users Only.
Perhaps you need to login or register.
13.1, 13.0, 12.2, 12.1, 12.0, 11.3, 11.2, 11.1, 11 or later
Linux, Mac, Windows
17 Aug 2022
1263
The default plugin is a visual approach to let you create knob defaults inside Foundry’s Nuke on the fly without the need to write and maintain any line of code. It contains the default main window which lets you create, edit and delete knob defaults and bundle them in preset lists that can be imported and exported and thus be shared with other artists.
Updates
----------------------------------
5.0
- Make Nuke-12 and Nuke-13 ready.
4.0
- Made Nuke11 ready.
- Major code changes.
- Wrote documentation.
3.2
- Security validity check on xml files which can reset them if there is a
problem and if the user chooses to do so.
3.1
- Small bug fix in the validity check of nodes and knobs.
3.0
- Default window: shows all your custom knobDefaults. You can add new custom
knob defaults and edits and delete your custom knobDefaults directly inside the
default window. The default window is accessible through your menu bar:
Scripts->default->defaults window.
- About window: manual which shows you how default works: The about window is
accessible through your menu bar: Scripts->default->about.
- Added functionality to create presets. All knobDefaults can then be saved within a
preset. You can create multiple presets which can be edited, imported and
exported.
2.0
- Right click a knob and choose default -> show knob list. A pop up window
appears showing all knobs of the node. Choose a knob and set its new default
value. With that you get access to set default values of all knobs of each
node, even if it's a drop down.
1.0
- Initial commit.
----------------------------------
Default will now contain a detailed documentation that shows how to install and how to use it. The documentation can be found in default/docs/_build/html/index.html
How to instal default
Download default and copy it into your nuke home directory.
In your init.py add this line:
nuke.pluginAddPath('default')
Further information can be found here:
http://www.leafpictures.de/default
Comments
Thank you very much
I already told you that was very useful :) . . Cheers..
Thanks again, I really appreciate it.
I get that you've put a ton of work into this and that's appreciated but thought I would ask since I wanted to customize something for our facility ?
Thx
But bad news ^) tool not working with expressions
https://s.mail.ru/YtFq/hjUfbnwwH
generates some interesting effects ^) like additional views creation
Sorry, just seeing this comment now. Your posted link is dead. Could you post it again?
Cheers, Simon
It is working good ,
But It is not working for expressions and for matrix also!
I use it on a lot of expressions. Which exact expression do you need to accomplish?
"... error interpreting this plugin"
It's the last line that's causing the failure:
# Auto load knob defaults when launching.
helper.load_knob_defaults(init=True)
After commenting out the last line everything loads correctly but won't work. If I try to save a default Nuke reports:
"[Errno 13] Permission denied: '/Users'
I tried creating a "Users" directories everywhere: /Users, ~/Users, ~/.nuke/Users and ~/.nuke/default /Users ... none seem to help.
You seem to get a permission denied error as all the mentioned paths don't seem to be the correct ones. There should be no 'Users' folder created manually.
I just double checked the script on centos and it seems to work fine on my side. Which distro are you using? Please see if putting the extracted default folder into your nuke home directory and then adding it to nuke's plugin path works out for you:
nuke.pluginAddPath("default")
I hope that helps.
Cheers, Simon
I'll try a fresh copy unpacked on the Linux box and see if that makes a difference.
I'll post the distro when I get to work. We are using Centos.
Thanks.
Release 7 (Core) 64-bit
Kernal 3.10. ...
Thanks!
I like that it works on the root project as well.
Thank you!
This is great ! I just used it on nuke 12.0 Just one issue, it does not seem to save any edit in defaults window. I cannt add any presets. Does anyone has any issue with this in nuke 12 ?
I have a small problem, when I set as default the value for Ramp p0 x and y, instead of putting the value in y it create another view and put it in x. I dont remember how to make it work for nodes with one/multiple values.
And just a proposition, could be nice in defaults window to click on name and have them class alphabetically, I have dozens of nodes and begin to be hard to find them ^^
thanks so much!
max
Thanks~
Nuke uses an own notation for colors. Using the following value should work, at least it does on my end, please give it a try:
4294967295
This is how I got there:
Adjust the color value of the Backdrop node as needed, in this example pure white. And then ask for its value by selecting the Backdrop node and executing the following:
print(nuke.selectedNode()["note_font_color"].value())
I hope that helps.
Cheers, Simon
ie. I have my menu.py that contains my specific knob defaults. But I work at a larger company, and often defaults are made on a show or even scene level. Done by having different menu.py files in the path.
I'd really like the option to see those.
Now, I know I can't change them directly, because that would involve altering menu.py files that feed to everyone else on a show.
But my personal menu.py, in my home/.nuke directory can over ride those show level defaults.
I guess it all depends on if we can see what defaults have been set in Nuke. I've been looking to see if its even possible to view the knob defaults. But I can't see any way of doing it.
'Seeing' all knob defaults that are done in your facility in any place might be a little more involved but this is how you could get that info. Basically you could loop over all dirctories in your nuke.pluginPath (), see if there are any init.py or menu.py files and parse these for lines that contain nuke.knobDefaul t. Note that these files implemement knobDefaults at an earlier stage and Nuke keeps no record when they are registered. That is why parsing init.py/mnu.py would be necessary.
As mentioned above, all knobDefaults should be set via an init.py to ensure same behavior between terminal and GUI sessions.
I hope that helps.
RSS feed for comments to this post