Open EXR layer bit depths differ in Output Properties and Compositor File Output #87988

New Issue

Saku Partamies · 2021-05-02T14:30:47+02:00

Saku Partamies commented

2021-05-02 14:30:47 +02:00

System Information
Operating system: Windows 10
Graphics card: RTX 2080

Blender Version
Broken: 2.92 release

Short description of error

I am not sure if this is considered as a bug, but as it is inconsistency in EXR file saving I report it here.

Open EXR file format can save different bit depths for different layers in one file and Blender supports this when render output is saved using main Output in Output Properties. This can be verified by saving a render with utility passes like Z-Depth. If output format it specified as 16bit (Half Float) other layers are 16bit, but Z-Depth and Vector layers are 32bit. This is wanted as those render passes are usually expected to be 32bit for compositing.

But if saving same render with same EXR settings from Compositor using File Output, then all render layers are saved 16bit. This is not good for compositing and would require specific utility passes to be saved as separate file using additional File Output node as 32bit. Both saving methods should produce same type of output to be consistent for user and better is to allow 16bit and 32bit layers to be saved in one file to make possible to minimize need of additional output files. At least user should have possibility to save 32bit layers in Half Float EXR file using compositor. Compositor File Output is often needed to rename output layers correctly for compositing pipelines.

Also related to same 32bit issue: Both save methods save Cryptomatte layers as 16bit if Half Float format is selected, but Cryptomatte must be 32bit to be usable. This should follow same logic as Z-Depth that is saved as 32bit using Output Properties file save. So, Cryptomatte layers should be possible to be saved as 32bit in EXR no matter where saving is done and what is the main bit depth of the output file. This would be expected to avoid pipeline problems from 3D to compositing.

Attached image shows difference of 2 outputs.

Exact steps for others to reproduce the error

Open attached blender_render_output_bit-depth.blend -file and render animation. File has just 1 frame animation range prepared for saving example files.
It saves 2 files to /tmp/ -folder: One from Output Properties and one from Compositor File Output
Open rendered files in image viewer that allows to see information of saved layers in EXR files (DJV).
Compare bit depths of saved layers in images to see differences.

blender_render_output_bit-depth.blend

**System Information** Operating system: Windows 10 Graphics card: RTX 2080 **Blender Version** Broken: 2.92 release **Short description of error** I am not sure if this is considered as a bug, but as it is inconsistency in EXR file saving I report it here. Open EXR file format can save different bit depths for different layers in one file and Blender supports this when render output is saved using main Output in Output Properties. This can be verified by saving a render with utility passes like Z-Depth. If output format it specified as 16bit (Half Float) other layers are 16bit, but Z-Depth and Vector layers are 32bit. This is wanted as those render passes are usually expected to be 32bit for compositing. But if saving same render with same EXR settings from Compositor using File Output, then all render layers are saved 16bit. This is not good for compositing and would require specific utility passes to be saved as separate file using additional File Output node as 32bit. Both saving methods should produce same type of output to be consistent for user and better is to allow 16bit and 32bit layers to be saved in one file to make possible to minimize need of additional output files. At least user should have possibility to save 32bit layers in Half Float EXR file using compositor. Compositor File Output is often needed to rename output layers correctly for compositing pipelines. Also related to same 32bit issue: Both save methods save Cryptomatte layers as 16bit if Half Float format is selected, but Cryptomatte must be 32bit to be usable. This should follow same logic as Z-Depth that is saved as 32bit using Output Properties file save. So, Cryptomatte layers should be possible to be saved as 32bit in EXR no matter where saving is done and what is the main bit depth of the output file. This would be expected to avoid pipeline problems from 3D to compositing. **Attached image shows difference of 2 outputs.** **Exact steps for others to reproduce the error** 1) Open attached **blender_render_output_bit-depth.blend** -file and render animation. File has just 1 frame animation range prepared for saving example files. 2) It saves 2 files to /tmp/ -folder: One from Output Properties and one from Compositor File Output 3) Open rendered files in image viewer that allows to see information of saved layers in EXR files (**DJV**). 4) Compare bit depths of saved layers in images to see differences. ![blender_render_output_bit-depth_layers.jpg](https://archive.blender.org/developer/F10049839/blender_render_output_bit-depth_layers.jpg) [blender_render_output_bit-depth.blend](https://archive.blender.org/developer/F10049841/blender_render_output_bit-depth.blend)

Saku Partamies commented

2021-05-02 14:30:47 +02:00

Added subscriber: @SakuP

Saku Partamies changed title from ~~Open EXR bit depths different from Output Properties and Compositor File Output~~ to Open EXR layer bit depths differ in Output Properties and Compositor File Output

2021-05-02 14:32:41 +02:00

Philipp Oeser commented

2021-05-04 09:55:50 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-05-04 09:55:50 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser self-assigned this 2021-05-04 09:55:50 +02:00

Philipp Oeser commented

2021-05-04 09:55:50 +02:00

Can confirm, will check on this

Philipp Oeser commented

2021-05-04 14:36:36 +02:00

Also related to same 32bit issue: Both save methods save Cryptomatte layers as 16bit if Half Float format is selected, but Cryptomatte must be 32bit to be usable.

Could you report this separately? Having only one issue per report makes the whole process easier.

> Also related to same 32bit issue: Both save methods save Cryptomatte layers as 16bit if Half Float format is selected, but Cryptomatte must be 32bit to be usable. Could you report this separately? Having only one issue per report makes the whole process easier.

Saku Partamies commented

2021-05-05 10:38:12 +02:00

In #87988#1155813, @lichtwerk wrote:

Also related to same 32bit issue: Both save methods save Cryptomatte layers as 16bit if Half Float format is selected, but Cryptomatte must be 32bit to be usable.

Could you report this separately? Having only one issue per report makes the whole process easier.

My bad. I created new report just for the Cryptomatte bit depth. I wanted to edit my post here to overline Cryptomatte part of the report, but didn't know how to do it.

> In #87988#1155813, @lichtwerk wrote: >> Also related to same 32bit issue: Both save methods save Cryptomatte layers as 16bit if Half Float format is selected, but Cryptomatte must be 32bit to be usable. > > Could you report this separately? Having only one issue per report makes the whole process easier. My bad. I created new report just for the Cryptomatte bit depth. I wanted to edit my post here to overline Cryptomatte part of the report, but didn't know how to do it.

Philipp Oeser removed their assignment 2022-01-18 21:08:59 +01:00

Philipp Oeser commented

2022-01-18 21:08:59 +01:00

Will have to concentrate on triaging for a while (and step down).

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Open EXR layer bit depths differ in Output Properties and Compositor File Output #87988