I usually use sub directories for stereo images with a change in filename. Basically, everything is the same, except that the stereo images had “_left” and “_right” at the end of the filename.
directory “3D_RENDERS\DT_01_v02_Beauty_Left”
Filename “DT_01_v02_Beauty_Left0000.exr”
It would be simple enough to duplicate the slate across the 2 images so it can be read in 3d.
Does this help?
Fred
My apologies for the delay… I was having some problems with hardware today. I’ve got it done now, but Paul noticed some bugs in the original script, so he wants to have a look at my modified script before I post it here. If he doesn’t post it tonight, I’ll post it in the morning.
Edit: Oh, and I was running the script through the Deadline Monitor… if you’re using an integrated submitter, we’ll probably need to make some changes.
Cheers,
Andrea
Were using RPManager for sumbmitting 3d jobs to deadline, and the regular submission script for Nuke. The naming and folder structure would be the same.
Hi Fred,
I’ve attached a version of the script that works for me, running from Deadline Monitor. When I run from the Deadline Monitor (rather than through an integrated submitter), I select one of the left or right images as the input file, and that sets the inFile parameter to something along the lines of:
3D_RENDERS\DT_01_v02_Beauty_Left\DT_01_v02_Beauty_Left####.exr
(using your example from a previous post.) The script then separates the path and file name, and creates separate patterns for left and right eyes with Left replaced by Right in both the path and filename for the right eye (or reverse for the left eye if a right eye sample was chosen). It is possible that the integrated submitter sets the inFile parameter to something else (for example, using %v), in which case the script will need modifying. If so, add a line that prints out the value of inFile, let me know what that value is, and I can adjust the script.
Another note: when I wrote the cookbook entry on stereo, I didn’t realize that the movie industry compresses the images horizontally so that the output frame width is not actually double. Paul has now brought me up to speed, and the attached script does this horizontal compression. (See this thread: http://forums.thinkboxsoftware.com/viewtopic.php?f=127&t=7557) If you do not want horizontal compression, let me know and I can change it back. If you know that horizontal compression is standard, let me know and we’ll update the cookbook example. (The stereo I was used to was from biology, and we didn’t compress horizontally there. Or, perhaps, we should have a version both with and without compression?)
Cheers,
Andrea
BENT_Slate_h264_24fps_stereo4.zip (2.22 KB)
Yes! It worked!
What would need to happen to make it work as a submission script? Is it about knowing where to find both left and right eye? Would it make it eaiser to drop the images in the same folder?
You’re referring to using an integrated submitter here?
That’s the main tricky bit that will change depending on how things are submitted, yes. I’m fairly new here and still learning the ropes with all the ways that deadline works, and have very little experience with Nuke, etc, so the more details you can provide me, the better. Are you thinking of the RP manager case, or the Nuke case? (For Nuke, are you using the Deadline monitor submission form, or an integrated submitter from within Nuke?
Thanks!
Andrea
I was just checking with Jon, and I have another suggestion for you… could you try running it as a regular submission script and then send me a copy of the logs for any Deadline job(s) created? Draft has enough output as it is that I can adjust it based on that. One complicating factor is that apparently a job will be created for each output when using an integrated submitter, so it might do something like create a job for each eye, one of which will fail because the data for the other eye isn’t there.
Cheers,
Andrea
Ok, Ill test it out fully as soon as I can. I thought about the double draft problem. I wonder if there is a way for the submission script to handle that, but I dont even know how draft even launches itself. Im in the dark on that.
Ill let you know how it goes for Nuke and RPManager.
Fred
Thanks! One thing I could do, once we confirm that it does indeed get called twice, is, if “left/right” is in inFile somewhere, I could check for that, and terminate one of the eyes early. Or I could do something where it deletes the movies if not all the data is there, but then it might still do lots of unnecessary processing, bogging down the render farm. Let me know what does happen, and I’ll figure out what we can do. (Monday, of course… I’m home for the weekend now.)
Cheers,
Andrea
While your thinking about these sorts of issues…
My current Draft script also makes movie files from all of the render elements generated from a completed job. Which can be great, but i’m wondering if there is an “easy” way to make a script that only does the main pass?
Just throwing it out there as a customer wish. 
Fred
You mean like using a subset of the frames? I’ll check with the Deadline folks, but one way is to submit directly to Deadline (you can set the frame range as a parameter there).
Edit: Paul’s updated me on what render elements are. I understand your question now. Will check with the Deadline team.
Cheers,
Andrea
So, I talked to the deadline team, and, although it would be nice to have, things would need to be a lot more integrated than they are now to be able to specify specific Draft jobs for specific outputs. Here are some options for the way things are now:
I’m guessing #3 is the best option, assuming there’s standard things we can check for in the path & filename.
Jon tells me that there’s an option for how jobs are submitted… either one job per node, or all output nodes in one job. (The latter is the default.) Is the latter what you’re doing? I think we’d be able to implement option #3 with fewer checks if you are.
Cheers,
Andrea
I understand and it seems to be tricky so ill be very happy with what i got. its nice to see element quicktimes of my velocity and zdepth pass anyways.
Were you able to test the script with the integrated submitter to find out what the command line arguments are being initialized to by Nuke?
Sorry, I got pulled away to a commercial job and wasn’t able to test the stereo rendering out of nuke. It did work with RPManager and 3dsmax
So are you okay now, or do you want me to modify the script so that it only runs once?
Cheers,
Andrea
Scratch that- It doesn’t work from RPManager, I think it worked when i ran it from Deadline. I’m doing a 3D test over the weekend so I’ll let you know. Ill post the error from submitting from RPManager if it will help.
Yes, that would help. I might be able to make it work.
Cheers,
Andrea