Cinema 4D version 4.02.1-R3 (Obsolete stable) Tweet

[aoktar]

Hi Ahmat. Thank you for this release.


I have a question:
Can there something be done about the rather large compression when saving OpenEXR from the octane save menue.
I usually save through C4D because of that. But with for example Render Layers Black Shadow, this is not possible (needs to go through Octane save dialog)

When I do that, I usually get much larger EXR files.

This is not completely release depended as I noticed that behavior in versions before.

Octane_EXR_Compression_01.png

I hope you see what I mean.
I would really appreciate if you can take a look an eventually come up with a solution.
Thank you for your great work.

I attached a simple scene file. Make sure the output paths are matching your machine.
As you probably understand it´s not about the scene, its about the EXR File size compared between C4D and Octane.

Cheers,
Raphael

You'll lose the some functionality if you use C4D's saving path for render layers. Always use Octane's saving path for passes and take a look for new EXR-Octane type. It's just not supporting the RenderLayer Masks but rest should be ok with good compression.

[Silverwing]

You'll lose the some functionality if you use C4D's saving path for render layers. Always use Octane's saving path for passes and take a look for new EXR-Octane type. It's just not supporting the RenderLayer Masks but rest should be ok with good compression.

Yes I know that in some cases, when you need a alpha per layer, its better to use the Octane render layer output.

This is the reason why I am asking for the same compression size in the Octane output then what the C4D output is delivering.

The problem is that I often render animations with 200 and more frames. My workflow is centered around using EXR files.
When comparing both outputs with 200 rendered frames, I will get 5 MB + 2 MB + 7 MB times 200 for the C4D output which created 2.8 GB of disc space.

When doing the same with the Octane output you get much bigger files. 24 MB + 5 MB + 24 MB times 200. Which equals 10.6 GB of disc space.
So I have a overhead of 7.8 GB that could be prevented.

Maybe a thing to note here is since I am working with After Effects and do not want to use the ExtracroR plugin, I never work with layered EXRs. I am working with single non-layered frame sequences.

I have looked in to the EXR (Octane) file. This unfortunately does only save a multilayer file. So its not usable for my workflow.
If there is a possibility to save EXR (Octane) Files with better compression (as you mentioned) withing single frames (not multi-layer) then I think I would be happy!

So in conclusion the only thing I am asking here is a way to save the EXRs with the same small size as C4D does, because it behaves the same and looks the same. The only difference is the used space. And I do not want to waste that much space on my HDD every time I render an animation

I understand if there is a limitation. I just wanted to ask if it is possible

[Tim_Twisted]

I have looked in to the EXR (Octane) file. This unfortunately does only save a multilayer file. So its not usable for my workflow.

If i'm understanding your problem correctly what you need is the checkbox beneath the render passes tab which says multilayer file. You get separate exr files this way.

[Silverwing]

I have looked in to the EXR (Octane) file. This unfortunately does only save a multilayer file. So its not usable for my workflow.

If i'm understanding your problem correctly what you need is the checkbox beneath the render passes tab which says multilayer file. You get separate exr files this way.

Thank you for taking the time to reply Tim.
Unfortunately that´s not it

I am arguing that the EXR saving dialog in the Octane Multipass save settings compresses the files weaker then if I do the same in C4D.
If you go a page back, you can see my initial post (also with unticked multilayer file box)
viewtopic.php?f=85&t=70622&start=10#p356857

Ahmet answered that with the new EXR (Octane) option in the list (see attached image) there is proper compression. But when choosing the EXR (Octane) option, you are no longer able to save non multilayered files.

So basically I am asking if its possible to have single non layered EXR files from the Octane Multipass section that are equally (small) compressed then what I get via the C4D save dialog.

[aoktar]

@Raphael: I'm using C4D's File Save functions and compression is not working well for EXR. I had some talk with Maxon guys but I couldn't get any solution from them. I can try to use our file saving function on EXR for individual layers but it will require some extra calculation and coding.

[aoktar]

Another thing - unrelated to UI slowdown (perhaps)
Since updating to 4 stable, when rendering to PV, hard disk space is continually taken up by files in the C4D prefs folder, subfolder "pv" with names like 9524709.b3d. Each one is around 230mb.
Is this an Octane thing or something else? After some time this fills the remaining 50gb space I have on the system drive and I have to purge manually.

We don't write anythings like that at least in plugin side. Please try without another plugins

[Silverwing]

@Raphael: I'm using C4D's File Save functions and compression is not working well for EXR. I had some talk with Maxon guys but I couldn't get any solution from them. I can try to use our file saving function on EXR for individual layers but it will require some extra calculation and coding.

Thank you very much for your answer!
Sad to hear that the maxon guys do not have any solutions for you.

If you have more important things to do, than do those fist of course.
I can help myself with the options that are available right now. But I would appreciate it if you keep that "task" (to write a EXR exporter) to the back of your head for when there is time.

Cheers,
Raphael

[Tim_Twisted]

Ah, got you. Didn't know there was a new EXR (octane) setting. Interesting stuff, will keep an eye on this thread.

[aoktar]

Indeed there was not... I already sent you a file in PM explainig this bug - you answerd me with a R19 test version wich unfortunatelly I can't test since I'm a R20 user.
I will explain again: shaders coming from files created with v1, v2 won't be able to use this different BRDF models other than "Octane" in V4, no matter how many times I toggle it's option.
Cheers,

Interesting, I cannot still reproduce that on me. Looking again!

EDIT: Found the reason of the issue and fixed, thanks for scene!

[aoktar]

Updated the version to 4.02.1-R2 with some quick fixes. Uploading and finishing the release notes...