Modo - file name from Optional Output

Deadline
1

We’ve been moving towards rendering out more layered EXR’s since we brought Nuke in house. This has been helped along by the fact that Deadline now respects Pass Groups when rendering with the Optional Output. But there is one annoying little bug that I’ve been trying to hunt down. When I render with no pass groups entered I get a proper file name like so:

JamesTest_07_v002_JB_0001.exr

But if I enter a pass group, Deadline doesn’t seem to respect the Output Pattern formatting from Modo. So the file names come out like so:

JamesTest_07_v002_JB_Left0001.exr

The problem being that there is no underscore between Left and the number padding. I was hoping that this is a basic script fix so I’ve been searching through the ModoSubmission.py to see if there a spot where the PassGroup name and the frame padding gets appended to the file name but I haven’t spoted it yet if it’s there. Any ideas from the Dev team?

Thanks!

James

2

Found the solution. In the Modo.py there’s a line at 220:

self.SendCommand( "item.channel outPat \"[<pass_>][<LR_>]<FFFF>\"", True )

I added the underscores in order to separate the pass group name from the frame padding.

EDIT:

OK, so this didn’t work. I should have looked more closely to the file names. What’s happening is that the pass groups aren’t being rendered. Not sure why this small change would break that functionality, but I’ll keep poking around.

3

OK, so I found that this change actually works and I get the proper name formatting and I get both passes.

self.SendCommand( "item.channel outPat \"[<pass>][<LR>]_<FFFF>\"", True )

This is the end product:

JamesTest_07_v007_JB_Left_0001.exr
JamesTest_07_v007_JB_Right_0001.exr

4

Cool. Glad you worked it out.
Mike