Render local and keep working?

[Randy Little]

I have been told I can't render a write node and keep working on a script with out causeing problems is this true?  So when the farm goes down I have to just render and take a nap? 

Also is there a way to render local and tell the render to only use half my procs so I can keep working? or is nuke smart enough to make the render a background task and give more priority to the forground task.  (this is on a windows xp 64 running 5.1v1b14) I hope we are updating end of the day. to 5.1v2

Randy S. Little
http://reel.rslittle.com

[Sean Falcon]

What's worse on OSX is the fact that if you do a local render through the GUI and put nuke in the background or minimize it, it will pop back up when it starts to render the next frame and continue to do so. Flipbooks do this as well.  This hasn't changed on 5.1v2. 

I believe -m  controls the threads used through the terminal during a render.

[Diogo Girondi]

Let me understand this, you want to keep working on the very same script that is being processed locally?

If so that doesn't make any sense for me for the simple reason that Nuke is using that script, just render it on the terminal (shell) and work in a new version in Nuke.

Or open a second instance of Nuke with a new version of that script in there.

Having the render progress bar focusing Nuke at each new frame must be a pain, but at least you can render in the terminal as an option.

[Randy Little]

Yeah in shake it makes a temp of that script and renders it.   Some times I render frames instead of flip booking.  I may not want to render up for a plethora of reasons. 

Randy S. Little
http://reel.rslittle.com

[Sean Falcon]

The big problem is that it happens on flip-books. So if I go to flipbook a seq....then I  might as well go outside and shoot some hoops while it takes over my computer. Playing a cached timeline is nice too, but I can never get respectable frame rates with big comps.