32bit SAVING NOT WORKING

[neonZorglub]

Hi Richard,

The saving as 3dsmax EXR is possible with non clamped values if you use a linear raw ocio view.

For example, unzip this
https://github.com/sobotka/filmic-blend ... master.zip
and, in Octane preferences / Main, set 'OCIO: Specify config file' to the ocio file, like
C:\ocio\filmic-blender-master\config.ocio
and enable 'OCIO: Use specified config file'

Then, in your current Imager, set the OCIO view to 'sRGB: Linear Raw'

That will keep the image as un-clamped 32 bits float per pixel, and will be saved by 3dsMax EXR.

I hope that helps.

The option I will add in the next release will do the same thing, without any ocio settings..

Thanks

[richardyarlett]

how do I save a "responsed" image as a 32bit EXR ?

[elsksa]

And for my other question... how do I save a "responsed" image as a 32bit EXR ?

It is merely counterproductive and unreasonable to encode in an integer fashion, a data set, in a 32-bit floating point OpenEXR container, out from the renderer specifically.

First and foremost, for non-data AOV, 16-bit hf should be used, as previously mentioned.
Any data AOV requires "unclamped", radiometrically linear and 32-bit floating point precision encoding.
There is a brief section about it on this page.

[richardyarlett]

Parade and neonZorglub, how do I save a "responsed" image as a 32bit EXR ?

[neonZorglub]

Parade and neonZorglub, how do I save a "responsed" image as a 32bit EXR ?

Hi Richard,

As far as I understand, I think you can't.

A 'responded' image can be saved as 32bit EXR, but values will be clamped in the range [0.0, 1.0] (sRGB)

In Stand Alone, if you save as EXR, you have the option to 'Force tone mapping', but you it needs to transform values to the [0-1] range..
As the tooltip mention:
"Whether to apply Octane's built-in tone mapping (before applying any OCIO look(s)) when saving a render result in a color space other than sRGB. This may produce undesirable results due to an intermediate reduction to the sRGB color space."

In 3dsMax, the same option 'Force tone mapping' is in Kernel / Passes output, when saving as Octane EXR.

To keep full floating point range ('unclamped' / linear), disable 'Force tone mapping' for saving as Octane EXR.
And in the lastest plugin versions (12.22 / 13.04), I added a 'Force linear' option in the imager, for saving as 3ds max EXR.
viewtopic.php?f=27&t=80190
You can also use the pixel color display to see the floating point rgba values..

But both way will disable any tone mapping..
That's the way Octane process the image, and I guess the way the math behind it works, as elsksa mentioned.

[richardyarlett]

So if I were to save an LINEAR, is there a good post rendering technique in PS to apply TONE MAPPING there ? Is there a plugin you are using to apply the same "response" curves in PS ? Because LINEAR is too harsh for me. I like a softer, warmer look.
When I reduce the highlights by turning on HIGHLIGHT CLIPPING to 1.0, even in LINEAR, it shows in the viewer, but it does not affect the RAW EXR. It still comes with HOT highlights. Is that a bug ?

[elsksa]

So if I were to save an LINEAR, is there a good post rendering technique in PS to apply TONE MAPPING there ?

Same principle as in Octane, to conform from linear to desired output, the "sRGB EOTF" is needed. But it won't suffice, as explained in the links I have shared, like this one. Not to mention how PS is inappropriate for "CGI-post" (conformation, compositing, etc).

Is there a plugin you are using to apply the same "response" curves in PS ?

A compositing software like Nuke, Fusion or even the free Blender Compositor, offer that, natively and properly (based on a "32-bit floating point precision engine").

Because LINEAR is too harsh for me. I like a softer, warmer look.

Linear is not a look, and it's never meant to be displayed without a transform/conformation first.

When I reduce the highlights by turning on HIGHLIGHT CLIPPING to 1.0, even in LINEAR, it shows in the viewer, but it does not affect the RAW EXR. It still comes with HOT highlights. Is that a bug ?

It's not a bug. The linear EXR is basically the raw rendered light-data (simply said), it should never contain any subjective transform/manipulation. It's mentioned on this page.