Multi frames render v1.2


 
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Serhat Baykal
A script for launche multi instance of nuke render with split frame range for each one.
Requirements:
10.5, 10.0, 9.0, 8.0, 7.1, 7.0, 6.3 or later
Windows
31 Mar 2017
299

A script for launche multi instance of nuke render with split frame range for each one.

_____________ v1.1
Replace the commande '-i' by '-x' so the tools doesn't take a nuke_i license but nuke_r ( render license ).

_____________ v1.2

Fix for render multi write node.

 

# input in your menu.py :

import renderMultiFrame1v2

customPlugin = nuke.menu('Nodes').addMenu('Custom Plugin')
customPlugin.addCommand('render Multi frame', 'renderMultiFrame1v2.main()')

Please login in order to download these files.

Comments   

 
0 # julien sabatier 2017-02-07 07:20
Ah Yes, merci bcp Serhat !
ju
 
 
0 # Mateusz Wojt 2017-02-09 11:34
Not working on Linux - you need to pass 'shell=True' argument in subprocess call if you want it to work properly.
 
 
0 # Serhat Baykal 2017-02-16 17:04
Apparently "shell = true" can be security hazard.
I don't work on Linux but if you can give some feed back I'll certainly work in on =)
 
 
0 # Thomas Vu 2017-02-16 18:15
will you make it work with multi write note ?
currently its not working.
 
 
0 # Serhat Baykal 2017-02-22 13:33
Hello,

If you unchek 'Selected Node Only' it doesn't work for multi write node ?
 
 
0 # Thomas Vu 2017-03-03 03:49
its not working sir, non frame renderd if i select all node or uncheck that menu.
 
 
0 # Serhat Baykal 2017-03-06 10:39
I publish a new version 1.2 it fix the issue for multi write.

I did a test and it works in my side, I'll appreciate if you can confirme it work in your side too :)
 
 
0 # Thomas Vu 2017-03-07 04:31
for the render all write node (uncheck selected node) its working now, thank you!
hopefully in next version you will add few more fuction like:
force create folder, and multi selection write note only (ex: render 3 of 5 write node)
 
 
0 # Serhat Baykal 2017-03-31 16:46
I work on a process to create folder !

For render multi write node you can do it with this version. Just disables the writes node you don't want to be render and uncheck the option 'Selected node only' !
 
 
0 # Anthony P. 2017-03-16 16:04
Hi Serhat,

Many thanks for writing and uploading this script!
Unfortunatly, when pressing the render button, i can see the render window start and immediatly shut down without an error message in the nuke log window. I'm using Nuke 10.0v3 and rendering stereo. Any idea what could be going wrong?

Also i had to change

import renderMultiFrame
to
import renderMultiFrame1v2

Kind regards,

Anthony
 
 
0 # Serhat Baykal 2017-03-31 16:41
Hi Anthony,

Indeed I totally forget to update the import line !
Thanks.
 
 
0 # Thomas Vu 2017-04-09 15:00
Might you fix it ? i dont know why i can not render by your script (normal still working fine), there is no gizmo node, only built-in node
https://youtu.be/n2gmhNJJNk8
 
 
0 # Serhat Baykal 2017-07-29 16:54
Hi, can you show me the output on the script editor ?

This happens to me when I let my script in proxy mode before launch the script !
 
 
0 # Thomas Vu 2017-08-02 06:37
Hi Baykal,Is possible to render with some custom gizmo?
Currently not working
 
 
0 # pankaj deshmukh 2018-07-05 09:02
Not Working
 
 
0 # prabin bhandari 2020-05-11 02:46
how to use
any one ???
 
 
+1 # Mattia Bruno 2021-11-08 12:05
Please bump for nuke 13### :oops:
 
 
0 # Ran Xie 2023-12-15 04:59
For Nuke13+ users, if this doesn't work for you I may have found a solution.
In the renderMultiFram e1v2.py, line 91:

print cmd

Thanks to Python 3, that won't work anymore. But have no fear, just change it to:

print(cmd)

See if that works. I don't quite remember doing that myself but now it seems to work for me on Nuke 13.2v5
 
 
0 # Ran Xie 2024-10-20 22:34
If anyone's having issues with this Script, in particular the problem of it starting but then abruptly not working, I think I have figured out the issue.

Try and find out what OCIO Environment Profile is being used. For example - some Pipelines use ACES 1.3. Which means you'll need to set Nuke to use ACES 1.3. I've found that only then does this work all the time.

It's weird 'coz the problem that comes up when debugging this was actually about Frame Ranges for some reason instead of strictly because of OCIO settings.
 
 
0 # Thomas Vu 2024-10-30 05:30
I still have trouble with this script, it starts then abruptly like yours.
I did check the color project and settings. that method not work for me... sadlly
 

You have no rights to post comments

We have 4423 guests and 163 members online