the other saved each channel as a separate file.
no time to diagnose.
Does Corona even support saving as multilayered exr? I have never seen an option for it.
Right now, instead of a single file, you are getting the "main" EXR + all other render elements saved separately as EXR files
Oh, this looks like you are not using any compression. Go to "setup" while you are defining the output and use zip compression or wavelet (yes, the latter is also lossless, no worries).
Good Luck
Is the below correct?
- You would like to save only a single EXR file with all render elements included in it
- Right now, instead of a single file, you are getting the "main" EXR + all other render elements saved separately as EXR files
---
One extra note:
If you use the "Save CXR" option and then convert your CXR to EXR, you will end up with a large file containing some layers which are normally hidden (for example information used to perform denoising). Maybe you are getting this kind of files? Could you send us some samples? The uploader is in my signature.
Hi,
Does this only happen when using backburner? Or does it also happen when rendering with Corona on its own?
Secondly, would you be able to provide a scene where this is happening for you? And I will do my best to investigate the issue.
Instructions on how to send the scene to us are in my signiture.
Thanks,
Rowan
That's how it is set up anyway, with ZIP compression.
That's how it is set up anyway, with ZIP compression.
In your original post, you wrote, the huge(r) files are layered. What makes you think so?
So what you've shown in the screenshot here (https://forum.corona-renderer.com/index.php?topic=25686.msg154107#msg154107) could be the result of setting up the render elements on a node/at a time where exr compression was switched off for exr output and then submitting/rendering it on another node with other exr settings; compression active that is.
All in all I think there are at least three topics mixed in this thread meanwhile? To sort it out:
- Original issue with large render element files (I suspect just uncompressed EXRs, see above)
- Issue having a layered EXR but also additionally all passes as extra EXR (that's how I misinterpreted it, cause: local settings)
- The dependency between main output file type and render elements file type(s) as denisgo22 mentioned
As for the latter: It seems that even if you do not explicitly specify a file name/type for a render element (usually a bad idea), the exr settings at creation time get stored and are not adopted from the current main output settings. At least compression settings - have not tested others. Well, that's new to me :)
we have been unable to reproduce this behaviour yet.
we have been unable to reproduce this behaviour yet.
What exactly have you tried? Remember that you have to send the scene through Backburner/farm (another node) to at least get the effect of layered EXR+extra EXR for every render element (RE) in some cases.
Here are questions for you:
1. when using CXR as output and having additonal REs defined. Should there be a) only a single, multilayered CRX as output or b) the multilayered CXR plus additional CXRs for every RE? If b), what is it for?
2. when using EXR as output and having additional REs defined AND you have ticked "Automatically Add/Remove Render Elements" in Render Output File -> "Setup". What do you get when a) rendering locally and b) sending it through Backburner? Please use the attached script as prerender script in Render setup -> common -> scripts to log the current state of the EXR output settings on the node(s) into max.log. My findings are: it depends on local settings (that's what the script reports, don't worry it does not change anything). This should never be the case.
Good Luck
1. when using CXR as output and having additonal REs defined. Should there be a) only a single, multilayered CRX as output or b) the multilayered CXR plus additional CXRs for every RE? If b), what is it for?
2. when using EXR as output and having additional REs defined AND you have ticked "Automatically Add/Remove Render Elements" in Render Output File -> "Setup". What do you get when a) rendering locally and b) sending it through Backburner? Please use the attached script as prerender script in Render setup -> common -> scripts to log the current state of the EXR output settings on the node(s) into max.log. My findings are: it depends on local settings (that's what the script reports, don't worry it does not change anything). This should never be the case.
Hi Dan
We are looking into this, but so far we have been unable to reproduce this behaviour yet.
Do you have any further reproduction steps which may help us?
Thanks,
Rowan
Well, that's annoying. I have no idea how you're going to reproduce the issue then.
We just submit the job as normal to BB and the render is spat out a while later, there's no script or special process that we follow, we just use max's native functions.
Well, that's annoying. I have no idea how you're going to reproduce the issue then.
We just submit the job as normal to BB and the render is spat out a while later, there's no script or special process that we follow, we just use max's native functions.
Hi,
Which versions of Max and backburner are you using? I couldn't see this info in the thread..
Rowan
Hi Dan,
Can you send me a screenshot of your file save settings for exr?
Thanks,
Rowan
1. Scanline and EXR:
BB job A: Autoadd ON in output configuration when submitting the scene:
1) BB server local setting autoadd on: 1 layered EXR written (beauty + RE)
2) BB server local setting autoadd off: 1 layered EXR written (beauty + RE) plus 1 flat EXR (the render element)
BB job B: Autoadd OFF in output configuration when submitting the scene:
1) BB server local setting autoadd on: 1 flat EXR (beauty only), NO render element at all
2) BB server local setting autoadd off: 1 flat EXR written (beauty only) plus 1 flat EXR for the render element
---------------------
2. Scanline and CXR:
4 times 1 flat CXR (Beauty only) plus 1 flat CXR (the render element). No Alpha.
---------------------
3. Corona and CXR:
4 times 1 layered CXR written (Beauty + RE) plus 1 flat CXR (the render element)
---------------------
4. Corona and EXR:
BB job A: Autoadd ON in output configuration when submitting the scene:
1) BB server local setting autoadd on: 1 layered EXR written (beauty + RE)
2) BB server local setting autoadd off: 1 layered EXR written (beauty + RE) plus 1 flat EXR (the render element)
BB job B: Autoadd OFF in output configuration when submitting the scene:
1) BB server local setting autoadd on:1 flat EXR (beauty only), NO render elements at all
2) BB server local setting autoadd off:1 flat EXR written (beauty only) plus 1 flat EXR for the render element
You can see that Corona + EXR is exactly the same as Scanline + EXR, a weird Max issue - not bound to a specific renderer. And again you can also see the impact of local settings. Case B.1 is the reason for removing the script from here. (https://forum.corona-renderer.com/index.php?topic=25686.msg154347#msg154347)That post is still valid for me, since I was able to reproduce it with the newest versions available. Only B.2 and A.1 are correct results, B.1 is data loss in the worst case and A.2 creates annoying additional render elements as Corona CXR always does ;)
Good Luck
you mean:
In the mean time, it might be best to set a pre-render script in the scene which sets the EXR file saving settings before each render commences. I hope this can be a suitable workaround for the time being.