Nuke Scene Collector v2.1

This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Dave G
This is a shell script for OS X / Linux that reads Nuke files and collects Nuke script and all support docs to a location you specify.
7.0, 6.3, 6.2, 6.1, 6.0 or later
Linux, Mac
06 Dec 2015

Update: this is still available for download but I recommend using the Python version that is cross-platform and more powerful:

Free. Unsupported.
Please login in order to download these files.


0 # J Bills 2010-10-20 14:38
thanks, using this religiously now!
0 # Francisco Palomares 2010-12-13 02:30
Awesome. This is the solution we've been waiting for during a long time ago!
0 # darren coombes 2011-01-19 22:42
Hate to sound like an idiot, but how do i get this working?
0 # DAve G 2011-01-20 08:22
darren - drag the shell script .sh file into a Terminal window and before hitting enter, drag the nuke scene file into the Terminal so that it forms a text line similar to this: /Volumes/MYBACK /DOWNLOADS_MB/n /Volumes/HOME_R AID/WORK/temppo stlight.nk and then hit enter and follow the prompts.
0 # darren coombes 2011-01-20 15:32
Thanks Dave, i tried doing the above and it comes up with "Permission denied" (see below for terminal text)

Suite03:~ editor$ /Users/editor/D ownloads/nukeco /Volumes/RAID/0 _Misc/Texture Mapping.nk
-bash: /Users/editor/D ownloads/nukeco Permission denied
0 # DAve G 2011-01-20 15:46
ah - it looks like the script loses execution permissions when you download it, maybe for browser security reasons. Add execution permissions to the script in the terminal by entering this: chmod +x /Volumes/MYBACK /DOWNLOADS_MB/n - obviously the part after +x is the path to your downloaded script.
0 # darren coombes 2011-01-20 16:53
Thanks Dave, it worked on my laptop, but not on our system here at work. We unfortunately have spaces in between characters on some folder names, and it must be making the script not function properly. Something we may need to fix. Thanks
0 # DAve G 2011-01-20 17:38
that's why you should drag the file into the window, so that it's properly "escaped," in UNIX terms. There are two easy ways to fix the path with spaces: put a slash before the space or put quotes around the full path: /Volumes/HOME_R AID/file folder with spaces/doc.nk or "/Volumes/HOME_R AID/file folder with spaces/doc.nk"
0 # DAve G 2011-01-20 17:40
the server parsed my note about incorrectly taking out the back slashes. it should be /Volumes/HOME_R AID/fileBACKSLA SHHERE folderBACKSLASH HERE withBACKSLASHHE RE spaces/doc.nk
0 # DAve G 2011-01-21 19:52
I realized you were talking about spaces in the path to the documents or source files tripping it up so I whipped up a copy that works with those: . It will not work with file or path names that don't have a space in them so use one or the other until I add a check to an updated script. The problem is that Nuke scripts put quotes around paths with spaces in them and not around paths with no spaces, so it makes matching and replacing trickier. It's not much work to make it work for both but it's late.
0 # DAve G 2011-01-23 12:04
ok - I removed the link above because the 1.3 script I just submitted now works for both cases (spaces in path and no spaces in path, mixed or not).
0 # DAve G 2011-01-27 19:44
just a note for Linux users - I just noticed that Ubuntu puts single quotes around paths when you drag the folder into the terminal window. These quotes will trip up the collecting if around the destination path. Write out the path without quotes and it will work.
0 # khush LP 2012-03-16 07:35
would this work on a Windows platform? if yes then 1) how exactly??? 2)i need to archive some stereo setups... each read node has left and right eye renders and i have used the %V to load them both in the read node.
can i use this script?
0 # DAve G 2012-03-16 08:50
This won't work on Windows but there is a Python scene collect script here that should:
0 # Sebastian Metz 2012-09-06 09:59
Hi Dave,

first off: Thanks a lot for writing this script! Great functionality, which I could use ALL the time, IF there weren't those two things...
So please consider this a feature request ;-)

1. Make the script understand read nodes with the (Nuke 6.3v8) file sequence notation "path/filename_ ###.ext" instead of the "path/filename_ d.ext" thing. This forces us to go through ALL the read nodes/do a batch find/replace every time....

2. Add support for the project directory file path concatenation. At our site, since we are using Houdini for the 3D part and very much like the $JOB-variable method, we like to work with setting the Project Directory once in the scene settings and then taking advantage of relative read node paths.

What do you think?

Greetings from good ol' germany,
0 # DAve G 2012-09-10 09:53
thanks for the suggestions Sebastian. I needed to update the utility for some other stuff so I integrated your suggestion about #### sequence notation in version 2.0, which is now live. If you send me a sample scene that uses your $JOB variable, I can take a look at supporting that. Email a sample script to daveg at can-con dot ca -- thanks,

You have no rights to post comments

We have 2511 guests and 77 members online