Why the Octane Renderer overexposed my image either in... Tweet

[Ofcourse]

Why the Octane Renderer overexposed my image either in the Render Queue and also in Render Picture Viewer? The final imafe file on my drive is fine but the preview of the image being rendered is overbrighted...

I do remember that this started to happen at some point with some version of Octane when it rendered the same output two times... the one overbrighted and the Main right... Please help me why is it happens.

[aoktar]

Why the Octane Renderer overexposed my image either in the Render Queue and also in Render Picture Viewer? The final imafe file on my drive is fine but the preview of the image being rendered is overbrighted...

I do remember that this started to happen at some point with some version of Octane when it rendered the same output two times... the one overbrighted and the Main right... Please help me why is it happens.

It's because of color management of Picture Viewer. We cannot correctly communicate/manage it. Just disable to see expected results.

[Ofcourse]

Why the Octane Renderer overexposed my image either in the Render Queue and also in Render Picture Viewer? The final imafe file on my drive is fine but the preview of the image being rendered is overbrighted...

I do remember that this started to happen at some point with some version of Octane when it rendered the same output two times... the one overbrighted and the Main right... Please help me why is it happens.

It's because of color management of Picture Viewer. We cannot correctly communicate/manage it. Just disable to see expected results.

What do you mean by "Just disable to..."? What I should disable?

[aoktar]

What do you mean by "Just disable to..."? What I should disable?

I wrote that:
"color management of Picture Viewer"

[elsksa]

It might be the option that has to be disabled. I've shared a guide and a Cinema 4D specific screenshot here: https://www.elsksa.me/scientia/cgi-offline-rendering/octane-render-color-management

If it is what I think it is, it has nothing to do with exposure, but instead, transfer function.

[Ofcourse]

My another question is why octane keeping to rendering double time the each frame of my sequences? So after the job is done there are always two times the same sequence, but one is overexposed and another one is fine (_MAIN) in the name.

I read in your documentation that I should not use the C4D save options and leave it disabled and set this up in the octane render settings, but this does not help me out.

[elsksa]

(...) but one is overexposed and another one is fine (_MAIN) in the name.

Over-exposed ≠ "double EOTF"
Double EOTF aka going from Linear-sRGB to "conformed" (ready to display and for the web) sRGB applied twice.

Did you disable the Cinema 4D "Enable Color Profile" as shown on the page I've linked?
Did you follow the guidelines from that same link?

If unsure, it will be necessary to share all relevant settings: Octane Camera Imager + settings window ("preferences") + Cinema 4D color management related settings.

[Ofcourse]

Thank you for your willing to help here, I will respond later on today

[elsksa]

You are welcome. No rush, no pressure.