Hi!
We are having trouble rendering out stereo with nuke. Do you guys know why this would be happening? Here is an email that I received from the senior vfx artist at our company:
"It seems that the deadline rendering plugin for Nuke does not handle the multiview work flow. A real basic run down is that when you have a stereo pair combined using multiview, when its time to render deadline doesn’t handle the left and right channels appropriately. Through many tests it seems that the eyes get mixed up, and one eye renders as all black frames (sometimes the 2nd eye errors out). I attached a basic script that doesn’t render properly in deadline, but rendered on the desktop (at the workstation) or rendered command line does render properly. We did all sorts of tricks to make deadline think it was rendering what we wanted… but nothing worked, when we could get one eye to render it was always the same, the right eye… regardless of what we were trying to do. Often times it just rendered blank black frames. "
I’m also attaching a zip file that includes: a simple script as an example, the two source files, and the render results from each render situation (Command line, deadline, and local… showing that deadline would only render one of the eyes).
Thank you so much!
Frank
rendering_problems.zip (27.1 KB)
Hi Frank,
Thanks for posting a test script. I modified the read and write node paths and tested rendering from within Nuke, from the command line, and through Deadline, and the results were correct in all three cases (no black or missing frames).
Which version of Deadline are you guys using? You can grab the full version number from the Help -> About window in the Monitor. We’re testing against the 4.0 beta, which is due for release this month, but we would like to test it against the version you are using.
Also, can you post a few render logs from the Deadline job so we can take a look? You can find the logs by right-clicking on the job and selecting Job Reports -> View Log Reports.
Cheers,
Were the modifications you made to the script read/writes significant? If you did more than just point the reads and writes to the appropriate folders, let me know and I’ll it on our systems.
From Deadline: Deadline Version: 3.1.0.36430
FranticX Version: 1.0.0.36430
For the script I sent to you, here is the log:
[code]Log Message
0: Task timeout is disabled.
0: Loaded job: renderingProblems_v01.nk (009_050_999_71efbf0c)
0: INFO: StartJob: initializing script plugin Nuke
0: INFO: Handling stdout that matches regex “.ERROR:.”
0: INFO: Handling stdout that matches regex “.* seconds to execute”
0: INFO: About: Nuke Plugin for Deadline
0: Plugin rendering frame(s): 1
0: INFO: Stdout Handling Enabled: True
0: INFO: Popup Handling Enabled: False
0: INFO: Using Process Tree: True
0: INFO: Hiding DOS Window: True
0: INFO: Creating New Console: False
0: INFO: Render Executable: “C:\Program Files\Nuke5.2v3\Nuke5.2.exe”
0: INFO: Render Argument: -V -x “C:\Documents and Settings\david\Local Settings\Temp\renderingProblems_v01.nk” 1,1
0: INFO: Startup Directory: “C:\Program Files\Nuke5.2v3”
0: INFO: Process Priority: BelowNormal
0: INFO: Process is now running
0: STDOUT: Nuke 5.2v3, 64 bit, built Nov 12 2009.
0: STDOUT: Copyright © 2009 The Foundry Visionmongers Ltd. All Rights Reserved.
0: STDOUT: Loading C:/Program Files/Nuke5.2v3/plugins/init.tcl
0: STDOUT: Loading C:/Program Files/Nuke5.2v3/plugins/init.py
0: STDOUT: Loading C:/Program Files/Nuke5.2v3/plugins/setenv.tcl
0: STDOUT: Loading C:/Program Files/Nuke5.2v3/plugins/formats.tcl
0: STDOUT: Loading C:/Program Files/Nuke5.2v3/plugins/getenv.tcl
0: STDOUT: Loading C:/Program Files/Nuke5.2v3/plugins/tifReader.tcl
0: STDOUT: Loading C:/Program Files/Nuke5.2v3/plugins/tiffReader.dll
0: STDOUT: Writing G:/storage/share/dell/schaider/rendering_problems/renders/deadline_render_left_tk01.0001.tif
0: STDOUT: Writing G:/storage/share/dell/schaider/rendering_problems/renders/deadline_render_left_tk01.0001.tif took 0.06 seconds
0: STDOUT:
0: STDOUT: Writing G:/storage/share/dell/schaider/rendering_problems/renders/deadline_render_left_tk01.0001.tif took 0.00 seconds
0: STDOUT: Total render time: 0.06 seconds
0: STDOUT: Write1: G:/storage/share/dell/schaider/rendering_problems/renders/deadline_render_right_tk01.0001.tif: Input has no valid channels - nothing to write.
0: INFO: Process exit code: 1
0: An exception occurred: Exception during render: An error occurred in RenderTasks(): Error in CheckExitCode(): Renderer returned non-zero error code, 1 (FranticX.Processes.ManagedProcessAbort) (Deadline.Plugins.RenderPluginException)
at Deadline.Plugins.ScriptPlugin.RenderTasks(Int32 startFrame, Int32 endFrame, String_ outMessage) (Deadline.Plugins.RenderPluginException)
0: Unloading plugin: Nuke
Log Details
Log Date/Time = Jan 22/10 00:23:06
Frames = 1-1
Slave Machine = Bluemax09
Slave Version = v3.1.0.36430 R
Plugin Name = Nuke [/code]
Let me know if you need anything else.
Brad
Hey Brad,
The only thing we changed in the read and write nodes was the paths to the input and output files. I see that the error report does mention what the problem is:
But why it would error like that, I don’t know. The version of Nuke we’re using is 5.1v2, so it’s a bit older than the version you’re using. Not sure if that makes a difference (it shouldn’t though if it works from the command line).
If you guys are interested in just testing out the 4.0 beta, just follow the steps here:
viewtopic.php?f=10&t=2778
At the very least, you could set up the 4.0 beta repository and client on a single machine and test the same Nuke script to see if you get different results.
Cheers,