Modo 6.01 submitter script

[markusp]

Hi,

I have Modo 601 and tried to submit a scene using the rrSubmit_Modo_4.0+.py script (# Last change: v 6.01.40). The .xml file is created, but it does not contain all the lines. This is what I get:

<xml>
<RR_Job_File>
<DeleteXML>1</DeleteXML>
</RR_Job_File>

Is this an incompatibility with the new render passes in Modo 601?

Regards,
Markus

[schoenberger]

Render Layers are supported.
Layered EXR have also been supported.
Tiled images are also supported.
Stereo rendering is supported.

The update for the Modo 601 submission is missing with the new features that modo 601 introduced regarding rendering.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

About the first post:

This is what I get:
<xml>
<RR_Job_File>
<DeleteXML>1</DeleteXML>
</RR_Job_File>

I now tried various scenes in Modo 601 and did not got this problem.
You have set an output filename in your "Final Color Output"?
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

PS: http://www.royalrender.de/cms/downloads/fixeschanges/ search for modo.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

The new plugin is almost finished (re-write), but I am still waiting for an answer about getting Informations about passes via python from the Luxo support.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

Hi

I have to release an update today for the other fixes.
The modo plugin is re-written, but the only feature it supports is the new output pattern which had issues with the old plugin.

About the passes:
All I require is a python script command to get the list of all pass groups with internal and user-name.
I have written the question into the Luxo forum, no answer at all.
I had contacted the Luxo support and they have given the issue to a senior developer.
I reasked and they told me the issue was now given to a different developer as the first did not had a solution.

I also heard from a different source that there are perhaps python commands missing for the new pass functionality.

regards,
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[Benny_RR]

Hello.
This morning we have installed the update on RR in our Farm.

Found the new Submitter for Modo called rrSubmit_Modo_6.0+.py

But on all our machines in the office this plugin dont work.
The old rrSubmit_Modo_4.0+.py still works.

If i try to start the Script within Modo, only the shell is visible for a half of a second and gone. Nothing happens.

Ok, trying to get the scene with the stand-alone rrSubmitter (right-click on the clientwatch-icon), but the rrSubmitter cant load all Modo-Scenes, because the file-type is unknown !?!?

Old version works perfect, update dont work, company-wide.

Question 2: can the new Modo-Plugin Submitter for 6.0.1 handle the new Stereoscopic-Renderoutputs like SBS / Overunder?
The new Stereoscopic-Features in 6.0.1 dont work with the older (4) Plugin (crash).

Regards,

Martin

[schoenberger]

1.
Found the issue, the path to RR was not set by the environment variable.

The main difference between the old and the new plugin is that the new one will work with the output pattern.
That should not work with the old one.

2.
Does it crash on submission or on rendering?
Please upload a simple scene file via www.RoyalRender.de/upload.php
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[Benny_RR]

Hello.

1.) How can i fix this to myself, or i´ve to wait for an update?

2.) Do you mean crashing when i´m trying to render a Stereo 3D-Scene?
Ok, submitting in Modo 6 with the old Submitter version 4-Script let me submit a scene to RoyalRender without crashing during the submitting process.
But our slaves will render the left frame, and new in Modo6 is for Side-By-Side (or overunder, anaglyph etc.) the right frame have to be render with the same machine that was rendering the left frame. And then Modo stitch the 2 images into one image sidbe-by-side.
After one frame (both left and right) is rendered from a slave, the slave stitch it and then crash.
That means, every slave can render one frame left&right, stitching and then crash. Sometimes no slave will render a Stereo-3D-Scene from Modo.

By the way, if i set inside Modo 6 the old pattern mode from Modo 5 in Modo 6 i can submit the scene with the old Submitter-Script (v4) in Modo 6, no problems.

Ok, no crashing during submitting with Script v4, no crashing during submitting with Scriptv6, but the v6-Script dont open the Submitter.exe

Thanks for your help, Royal Render is great !

Gruß aus München.

[schoenberger]

1)
Search for RR_Root.
Remove the # from the next two lines.

2) For now it seems to be something that is not fixable from our side.
RR tells modo the start and end frame and then starts the render function.
So if the frame starts to render, everything else is up to modo, there is nothing that RR does after the render starts.

I could only contact the modo support about that issue, perhaps send them steps to repro.
If I get the scene to crash. Which settings have you set to what to get the crash? (just to be sure nothing is missing and I do not get a crash, happens always)
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

Ok, got a little bit further.
Took me the whole day, but now I can get all groups.
Problem so far is that you probably use groups for something else than passes, right?

If everything fails, I will try to write a C++ loader for the modo files, if that is possible.
Then I do not have to fight with the commands available in modo scripting.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

About stereo rendering:
I tested side-by-side. No crash, no problem at all.
And I directly reported 4 bugs about stereo rendering and file naming.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[Benny_RR]

New problem detected.

Have a scene for rendering.
Sent this to RR, all slaves rendering.

For example: scene has a frame range of 500 frames.
Every slave has to render a set of 50 Frames.

Now:
if all slaves get the last sequence of 50 frames from RR, then every slave hang on the last frame of their sequence.

That means, last frame is rendering on every slave for seconds, then stop, RR sent the last frame to render to another free slave, this slave will try to render this last frame for seconds, then stop, RR sent this frame again to another slave and so on. Last frame will never be rendered.

There is no error, so the farm is working all night long to render all last frames of all sequences and other jobs are blocked because the job will never end....

Old script (v4) doent have this problem

[schoenberger]

Strange as the rendering part is the same no matter which script you use to submit.
Please select the job you submitted with v4 and the job you submitted witrh the new script.
(both should have rendered)

Then export the debug info of the selected jobs via the debug menu in rrControl.
Upload it via www.RoyalRender.de/upload.php
Then I can check for a difference in the job and in hte render log of the last frame.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

Ok, there is a new RR update.
It supports multiple cameras (you have to use <Camera> in the filename/outout pattern)
Tiled images
Passes (only glitch: it shows all groups, no matter if pass group or not)
The output path can be changed in the submitter
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

I probably found the issue and it is fixed.
(a difference in the new script that set the output of all layers to the same path)
But I cannot test it.
Even if I hit render animation inside modo, I only get the Final Color Output.


Then some info on the other issues:
The new submission script does not work in all cases.
As far as it seems the only solution is to write a scene parser for modo files.
Let's start hacking the file format...
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[Benny_RR]

Hello,
thanks for your help.

The fix will be available in the next update?

Regards,

Benny_RR

[schoenberger]

Trying to hack the modo file format today (started yesterday).
A new release will probably then be available this week.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[Benny_RR]

Wow !

But dont stress ! At this time i can live with the old version, it works ok for me.

Regards,
Martin

[schoenberger]

It has to be done at some time.
And right now I have everything fresh in mind that is required for modo rendering.
As I am working the last days on modo.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

Ok, good news.
I have hacked the file format.
As I do got any information, I do not know if it works with all modo scenes.

Please download
www.RoyalRender.de/download/120425_RR_modo601.zip

Copy the files into your RR directory.
Important: Copy the
RR\render_apps\scripts\modo_render_60.py
also into
RR\render_apps\scripts\rr_orginal\modo_render_60.py


After you have copied the files, do NOT execute the rrPlugin in modo.
Start the rrSubmitter and load the modo file.


It should read all pass groups, all pass output paths should be displayed at the job.
(The next version will also read all cameras so you can choose which cam to render and it will show the other layers output paths)
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

PS: the old submission plugin will not be affected by this plugin.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

OK, I got a scene that does not work. The SeqStart/End are not read sucessfully.
More analysing to understand their format....
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

Ok, next try:
www.RoyalRender.de/download/120425_2_RR_modo601.zip
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[Benny_RR]

Thanks!

I´m testing it today.

[larkis]

Should this also be working from the rrSubmitter that is on the mac ? It seems to be working on the windows version but not the mac one. Also .lxo does not appear in the file format list on the mac rrSubmitter.

[schoenberger]

Right now the plugin was only compiled for windows.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[larkis]

There is another issue I'm running into. I use modo on the mac but have to open the scene file on the PC and point the outputs to the proper location on windows (our renderfarm is windows based) in order for the files to render. I have path mapping configured in royal but it still seems like the modo slaves can't deal with re mapping the mac path's to windows ones. For some reason there is no issue with textures, only with outputs.

The error i'm getting on each modo node is:

R 11| ! ((unknown)) Saver failed with an unknown error.
R 12| ! ((unknown)) Image saved successfully.
R 13| ! ((unknown)) Saver failed with an unknown error.
R 14| ! ((unknown)) Image saved successfully.
R 15| ! ((unknown)) Saver failed with an unknown error.
R 16| ! ((unknown)) Image saved successfully.

So i'm not sure where the images are going and if they are going anywhere at all. There is certainly nothing in the folder I pointed the output to.

[schoenberger]

Hi

Do you mean that you cannot submit from osx or that the way you tried does not work?

Quick summary what you do:
Scene creates on OSX.
Loaded on windows.
Paths of all Layers changed.
Scene saved.
Scene submitted.

Can you use the "Render Animation" in modo on windows after you have done the changes and saved the scene?


Textures are probably saved in a relative path, so they are never a problem.
But because modo saves the texture paths relative, the client cannot create a local copy and change output paths in the scene file to windows.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

There is a new feature request to create new scene files for all OS on submission.
So you would have new files on every submission: scene_rrwin.lxo and scene_rrosx.lxo.
But this feature is logged for the next major update.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[larkis]

[schoenberger]

In RR, the client changes the paths.
But this is only possible with local scene copy and then relative paths do not work.
And as Modo uses relative paths, the whole feature does not work.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[schoenberger]

FYI:
The latest RR version has the new plugin by default.
Even if you use the rrSubmit via modo (actually just starts the submitter with the current file as commandline parameter)
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[nicoM]

Hi Holger,

testing the latest build of royalrender(6.01.70) with modo 601 SP2.
When I submit a scene (with the script or by loading the scene in the submitter) there are few problems:

1. The submitter didn't recognize the frames to render. I have to manually edit this.

2. Scenes with renderbuffer works when I submit as separates jobs but don't work when I submit the *All*.
With *All* nothing renders!!!

3. When I try layerdEXR the rendernodes crashs all the time. I have used .exr as a file format in the renderOutputs....

[schoenberger]

Please delete all geo and replace it with a sphere.
Then upload the scene via www.RoyalRender.de/upload.php
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[nicoM]

Hi Holger,

I have uploaded the scene .... it is called "rendertest.lxo"

Thanks

Nico

[schoenberger]

Hi

1. Your test scene has set frame 1-10, same as the rrSubmitter has read.

2. It is working in the latest RR dev version 6.2, but there was a small change in the modo submitter regarding layers.
Please do not submit the Layer "all", try to submit the layers as seperate jobs.

3. This is a modo bug.
RR just executes:
render.animation {*} openexrlayers
(according to the docs)
and that command crashes.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[nicoM]

Hi Holger,

thanks for your answers...

Is it possible to use the new modo - script (from dev. 6.2) with the current releas?
If it possible - could you share this new script?

thanks
Nico

[schoenberger]

Hi

No, that is not possible as the qt libraries are used by all applications.
And those will be replaced.
But 6.2 should be released tomorrow.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[JanJinda]

Hi there,
thanks a lot for modo script, everything seems working perfectly. Just one thing, I have output pattern in modo set to _<pass>.<FFFF> when I load it to submitter it's xxx_AO.#.tif. For postproduction it's crucial to have more digits then one. I have no problem to set it up in RR Submitter, but tell me how. Thanks a lot Jan

[schoenberger]

Please update to the latest version of RR.
Afaik the issue was fixed.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[JanJinda]

schoenberger: great, thanks a lot

[vertex]

[schoenberger]

I have logged it as improvement
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[larkis]

What is the current state of modo and royal working with modo outputs ? I want the ability to set one render path and have all the render outputs in the scene go to that path without having to specify each render output location manually. I'm on royal 6.02.06 and this functionality is not present. At the moment each render output needs to have the output location manually set. This is pretty frustrating when I have 20 render outputs and my scene version changes and I have to change 20 file paths.

Any advice would be great. When rendering locally using the "render animation" command each render output gets dumped into the same directory as the one I specified in the save dialogue. To bad this does not work with royal as it would save a ton of time.

[schoenberger]

Hi

I am sorry, but there is currently no workaround for this.
You can copy/paste the same path into all render outputs.
With the new output pattern in Modo 6.01 it will set the filename to a different name for each render output.

But the output pattern in modo does not support path names. I do not know if the modo team has logged it.
RR supports path names in the output pattern. I will log a change that you can leave the render settings empty, but use the output pattern for the path.

Disadvantage: You probably cannot use the render animation without RR as modo will not like it.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[larkis]

[schoenberger]

Hi

Modo requires to support a full directory name in the output pattern
So you can set a path and output name for all your layers.
_________________
Holger Schönberger
Binary Alchemy - digital materialization

[larkis]

[schoenberger]

Modo requires to support a full directory name in the output pattern

Just try this:
In the output pattern box of your scene file, enter
C:\MyNameProject\MyRenderings\Shot12\[<pass>][<output>][<LR>]<FFFF>

Right now you cannot set a path name in the output pattern box.
_________________
Holger Schönberger
Binary Alchemy - digital materialization