Our friends at The Foundry have added some new goodness in the most recent version of Nuke that makes it way easier to set up custom keyboard shortcuts. It’s so wonderfully convenient that I worked up a quick tutorial on Nukepedia to share the convenience.
In celebration of their 10,000th member, Nukepedia is giving away a Nuke license. I am most definitely not winning that contest, but holy cow — I’m on the list!
Nukepedia is an awesome resource. It’s so much more than a gizmo repository. It’s also a place for sharing tips and techniques and they also have a handy collection of reference data & images. It embodies the sharing spirit that makes the Nuke community so special. I couldn’t be where I am now if all those people on that list hadn’t taken the time to share what they know. Thanks to each and every one of you guys. I am super proud just to be on the same list as all of you.
I came up with this hack for Nuke because I am fundamentally lazy and detest manually updating output paths when I version up. The AutoWrite eliminates that manual work by looking at the Nuke script’s filename and path and auto-magically following along each time the script is updated. No user intervention required!
I have a little break in between shows right now, so I’ve started working my script for launching background renders from Nuke again. It’s now called “bgNukes” and has what should be a permanent home on GitHub. I’ll also try to keep it updated on Nukepedia, too.
I have two goals for it: make it work on any platform and any version from 5.2 to the current one and also provide feedback in the GUI about how the renders are progressing. both of these will require some learning on my part, but I wouldn’t have it any other way.
Update 4 September 2010: Because of some great feedback from Nukepedia, I added a feature to specify which render node (or nodes) are being executed. (Thanks Djati!)
I hacked up this script because I was frustrated with rendering in the Nuke UI, tired of typing out command-line render commands, and our renderfarm wasn’t alive yet. I’m posting it because I bet there’s other people in the same situation and I hope it can ease your pain.
This script launches a number of command-line render instances in the background and captures their output in log files which are saved to the same directory as the Nuke script. You are now free to keep working in the UI and have your renders happen in the background. You are also free to to launch 8 simultaneous command-line Nuke renderers and fully saturate your fancy 8-core MacPro. Continue reading →