Page 1 of 2

EXR not being saved with full dynamic range

Posted: Tue Jun 27, 2023 6:19 pm
by Dingbat
i've tried 16 and 32 bit exr options but any values above 1.0 intensity are clipped to 1.0

the image isn't linear either it's gamma corrected when i open in Fusion or Affinity Photo

the same image exported from MODO works as expected

Re: EXR not being saved with full dynamic range

Posted: Wed Jun 28, 2023 5:46 pm
by Dingbat
ACES/Force Tonemapping/Highlight Compression all disabled

is it working for you?

Re: EXR not being saved with full dynamic range

Posted: Wed Jun 28, 2023 6:34 pm
by Dingbat
clipping01.jpg
clipping02.jpg

Re: EXR not being saved with full dynamic range

Posted: Wed Jun 28, 2023 6:42 pm
by Dingbat
same process but rendered in MODO:
clipping03.jpg

Re: EXR not being saved with full dynamic range

Posted: Thu Jun 29, 2023 7:01 am
by face_off
For reference, saving an EXR saves with the following settings:

- sRGB color space
- No pre-multipled alpha
- Zlib compression, in blocks of 16 scan lines (lossless)
- Compression level of 45

There is an option to save as "The sRGB color space with a linear transfer function." (ie. Linear) - however that would apply to all saving of EXR's. Linear is potentially the better default for EXR's. Let me know if you would prefer that.

Thanks

Paul

Re: EXR not being saved with full dynamic range

Posted: Thu Jun 29, 2023 9:08 am
by Dingbat
elsksa wrote:I don't know where that EXR has been loaded to be viewed.

Has it been conformed to display output? From Linear-sRGB to non-linear sRGB?
A linear-sRGB EXR is not supposed to be viewed without a conformation to a given output destination.
thanks

i understand that a linear EXR is not supposed to be viewed natively. i was showing the linear image to point out the difference vs the tonemapped Archicad output

i should add that i wrote "the image is rendered in MODO" but of course i meant Octane for MODO

the post processing app is Fusion Studio. my usual workflow is very simple - export a float 16bit linear EXR and tonemap as required

same image from above tonemapped:
clipping04.jpg

Re: EXR not being saved with full dynamic range

Posted: Thu Jun 29, 2023 9:14 am
by Dingbat
face_off wrote: There is an option to save as "The sRGB color space with a linear transfer function." (ie. Linear) - however that would apply to all saving of EXR's. Linear is potentially the better default for EXR's. Let me know if you would prefer that.
yes please from me

those that prefer tonemapped have the png option, or can use the Force Tonemapping option (which should give the same result as what we have now?)

Re: EXR not being saved with full dynamic range

Posted: Thu Jul 06, 2023 8:14 am
by face_off
Here is a test release with the saving of EXR's from the "Save" and "Save All Render Passes" being done with the linear colorspace rather than sRGB. Let me know if you have any issues with this build.

https://render.otoy.com/customerdownloa ... _test1.exe

Thanks

Paul

Re: EXR not being saved with full dynamic range

Posted: Mon Jul 31, 2023 4:19 pm
by Dingbat
thanks Paul

had a go with this but there are still issues

the image seems to be saved linear, but max white values are clipped at 1.0 (they should go beyond 1.0)

also, tonemapping is saved. with linear workflow the image should be saved without tonemapping (unless Force Tonemapping is selected)

Re: EXR not being saved with full dynamic range

Posted: Tue Aug 01, 2023 11:24 am
by face_off
I think I have messed this feature request up - as there is a conflict between the new combobox and the Settings->Image Save Format. If you set the Image Save Format to EXR, does that resolve the problem?

Paul