This location is for Registered Users Only.
Perhaps you need to login or register.
11.0, 10.5, 10.0, 9.0, 8.0, 7.1, 7.0, 6.3, 6.2, 6. or later
Linux, Mac, Windows
汉化 Chinese Translations: See github.com/max-van-leeuwen/Nuke-WrapItUp
A big thanks to Skydream VFX for making these!
WrapItUp is an easy-to-use tool that can collect and relink almost all files required to make a Nuke script work on another machine.
It has a user interface if you run it in Nuke, it can be executed from a command-line window for batch operations, and it can be called using a Python function.
I made sure to cram the entire thing in just one Python file, so you can simply drag-and-drop the file it into Nuke's script editor if you wish to use it just once.
To quickly collect all files for a nuke file, simply choose an empty folder in the “collection folder” box at the top of the window and hit Start.
Tested on Windows, Mac OS, and Linux (CentOS).
Features and settings
- Three copies of the Nuke script will be collected: the original, a relinked one, and a relative-relinked one (using a python-embedded TCL expression).
The relative-relinked Nuke script will stay linked to its media, even if you move it to a completely different machine - as long as the media is right next to it.
- Media files with the path variables ####..., %**d (printf), %v and %V are supported.
- Gizmos will be collected, and the necessary menu.py and init.py files will be generated. Simply place these files in your .nuke folder to install them.
- A detailed CSV log file is generated to review which files were copied.
Not supported: Shared library plugins, (.dll, .dylib and .so files).
There are simply too many dependencies and licenses involved to keep track of these.
See my website (maxvanleeuwen.com/wrapitup) for more information about all features and settings in this script, and for command-line/Python use!
Standard Nuke installation
- Place the WrapItUp folder in your .nuke folder (or somewhere else on your computer)
- Go to your .nuke folder, and create a file called 'init.py'. If such a file already exists, open it.
- In the init.py file, add this line of text to the end and save it:
If you want to place the folder somewhere else than in the .nuke folder, make sure to change the path in the init.py file so that it points to that other path instead!
Only run once (in Nuke)
If you are only running it once, you can simply drag-and-drop the WrapItUp/WrapItUp.py file into the script editor panel in Nuke and click 'Run the script'.
Installation using NukeShared
- Place the WrapItUp folder in the '_AutoInstaller' repository.
NukeShared is a way of installing plugins by dragging/dropping them in folders, see this page for more information.
If you encounter any issues (or if you have feedback/ideas), let me know (maxvanleeuwen.com/contact)!
Fixed Nuke 10.5 compatibility
added support for media in Project Directory (root settings)
added interactive license (nuke_i) support (for internal use, when scripts are relinked)
added more information to log CSV
fixed bug with font folder relinking
fixed bug with 0b files freezing the copying process
relinking and relative relinking now only modifies knobs of media that is not user-ignored
fixed 'open folder' keyboard shortcut
added 'go to node' button
fixed error on empty project font path
fixed TCL support on font paths
fixed issue with gizmo's and nuke script containing dots in their names
UI labels now evaluate TCL as well
log now stores used nuke version
File paths with TCL are supported
Folder browser will ask to create new folders if the selected path does not exist
Added PySide support (for Nuke 10.5 and older)
Fixed Nuke closing on user interruption when 'exit on finish' is checked
Fixed Nuke asking to save your Nuke script when 'exit on finish' is checked and script has not been saved