bgNukes v1.2
This location is for Registered Users Only.
Perhaps you need to login or register.
5.2, 6.0 or later
Linux, Mac
bgNukes README
Overview
bgNukes is a tool for launching background renders from The Foundry's Nuke. It is written by Tim BOWMAN.
This script exists because our company renderfarm wasn't alive yet and I was already frustrated with rendering in the Nuke UI and tired of typing out command-line render commands to background the renders. I am sharing it because I'm sure my situation was not unique.
Originally, I posted it as launchNukes_inNuke.py (I know -- awful name) on VFXTalk and on my blog. As of now, the official home for bgRender will be on GitHub and it will be found also on Nukepedia.
How to install
Put bgNukes in your .nuke directory (or somewhere else in your Nuke path if you're fancy), then add this line to your menu.py:
import bgNukes
Importing the module adds a "BG Render" item to the Render menu.
How to use
Select the Write node (or nodes) that you want to render. (If you don't select anything, that's the same as if you selected everything.) Now select the "BG Render" item from the Render menu. In the panel, tell it which frames and how many instances you want and click OK.
Happy Rendering!
Details
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.
It works in Nuke 5.2 and 6.0 on OS X. One of my goals is to ensure that it works on Nuke5.2 to the current version as well as any platform. Maybe it already does. If you've tested it and it worked (or didn't) please let me know what happened.
Thank you
Thanks go to Nathan Dunsworth. His localRender.py was (and continues to be) an excellent reference.
LICENSE
Copyright (c) 2010 Tim BOWMAN
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Comments
how do i manage this BgRender ? thanks Tim.
by the way, its a good job my friend
so can i render all write node a,b,c with specific frame range ? because when i did render all --nuke always asking me the frame range--the default is 0-100. hope we're clear now ?
In the meantime, because it sounds like you have three different trees in your script, can you separate them into three separate scripts? That way you can set the frame range for each script and bgNukes' defaults will behave normally for you.
i'm running Nuke 6 on MacOS X 10.6 and try to use your script and i've this error when launching Nuke : menu.py :error interpreting this plugin.
When i delete the import bgNukes line, no more error.
Thank you for your help
so better we should make separate scripts rather than we make it collected. because while im doing grading, id like to be as a one script so if there's some shots had same lighting,ambien ce etc i shouldn't re-do the grading set. but it's ok Tim, im clear enuf for this.
once again Thanx man
Djati, now that I understand what you're doing, being able to specify which node to render becomes really important. I'll be sure to put that in for the next version.
Thank's a lot!
so when you 'll make it for windows platform ? coz i got 3 nuke stations runs on Win64bit on 7,:-)
cheers buddy
Kit
I ran the script it said it launched the background renders but I dont see any terminal windows popping up - is this the default? how do I monitor the bg processes? Also i had the first ten frames or so of my sequence already rendered - the bg render replaced them then nothing else was rendered. no logs either. Am i doing something wrong here? Also is there an option for 'skip existing files' in this script or in nuke ala after effects?
Thanks to Ryan O'Phelan, I've addded an update to bgNukes that should allow this script to run on Windows. The only problem is that I don't have access to Nuke at the moment and so I'm unable to test it. For that reason, I'm not posting it to Nukepedia because I don't want to distribute something that's untested.
This is where you come in. I have put the change in the GitHub repository for bgNukes [http://github. com/timbowman/b gNukes]. It is version 1.3. I would appreciate _very_ much if someone running Windows and someone running Linux/OSX could verify that everything's working and post their results here. If everything's good, I'll post the update ASAP.
Thanks in advance for your help and happy rendering!
-t
one thing that would make the usage of this script even better for me would be a convienient way to stop the background rendering if needed.
or for example to change the number of instances during rendering when a bit more resource is needed for the foreground work. i dont know how and if this can be done. at the moment on the windows system you have the option to shut down all the instances from the task manager one by one, which is usable but not too convienient.
thanks for the script it seems very useful.
andres
It shows dialogs but doesn't do anything
Visit this project on GitHub for a version that does work in Python 3 (at least on Windows.)
RSS feed for comments to this post