EXR Import/Export Settings User Feedback Required

[shijan]

Multi layered EXR format Import/Export is very special and may need some attention and suggestions/ideas from users who work with EXR files in real life in VFX and 3D apps.
Earlier i suggested layers auto naming for EXR to match PLD layers order. But in beta 24.40b4 due this automatic layers naming, exported EXR files have no preview in macOS Finder and can't be opened in some other apps. This happens because many apps that don't support multi layered EXR can read by default only unnamed layer.

PhotoLine in imported EXR adds layers into groups if EXR layers named as groupname.layername.
PhotoLine in exported EXR creates baked layers from Adjustment Layers.
EXR files rely on layers naming and can't remember layers position.
Some apps preserve original EXR recommendations for layers naming and structure, and some create their own naming system. Any sense to preserve PLD layers structure in exported EXR?
I guess perfectly EXR should be somehow imported, edited and exported from PhotoLine with exactly same layers structure and naming, so other apps could read edited file exactly same as original.

Some resources that may help:
Free Exr-IO Ps plugin that allow to read/write EXR files and have a lot of custom options that might be useful in PhotoLine EXR Import/Export dialog as well.
https://www.exr-io.com/reading-openexr-files/
https://www.exr-io.com/writing-openexr-files/

EXR example files
https://openexr.com/en/latest/_test_ima ... est-images

My small multi layered example rendered from Cinema4D using ProRender with layers numbering enabled:
https://www.dropbox.com/scl/fi/meex2bz9 ... 8vn0u&dl=0

[shijan]

Here is also side by side compare of Cinema4D_ProRender-with-layers-numbering test file opened in different apps:

PhotoLine (main unnamed layer automatically placed at bottom):


Krita (main unnamed layer automatically placed at top and virtually renamed to "HDR Layer". Exported EXR naming structure remains unchanged and there is no "HDR Layer" name in main layer. Very nice.):


Affinity (main unnamed layer automatically placed at top and renamed to "RGB", all layers are imported as separate channels also added additional naming tags. Exported EXR totally unusable, all layers painted in orange colors. Something is totally broken there):


DaVinci Resolve Fusion (main unnamed layer automatically placed at top. All layers are imported as separate channels. Only RGBA layers where detected automatically, but other layers could be assigned manually):

[Herbert123]

I use multi-layered EXR exported from Blender all the time for serious compositing in PhotoLine.

Working with EXR from different 3D apps and render engines, as well as how those EXRs are handled in various image editors and other software is a potpourri of pitfalls and varying workflows.

For the most part I like how it is solved in PhotoLine. The naming conventions work fine for me. I did notice that it can take a LONG time to import EXR files. Would be nice if that could be sped up a bit (or a lot!).

My main wish is that PhotoLine's EXR import and export would deal properly with Cryptomattes. Those do not work and are kinda essential nowadays - or at the very least make life so much easier.

For inspiration to improve the overall EXR workflow, check out the excellent EXR-IO plugin for Photoshop:
https://www.exr-io.com/features/

Although I do understand this would be asking for too much, some of that information could inform how to improve PhotoLine's EXR import.

To test, check out this Blender tutorial for EXR-IO. In the description a Blender demo file is linked to.
https://www.youtube.com/watch?v=43TRMeQZlzA

[shijan]

Just attempt to imagine possible realistic workflows for EXR files:

Possible Workflow 1:
Export EXR render from 3D editor -> Import to PhotoLine and edit layers -> Export to EXR -> Use edited file in some other VFX/3D app.
In this case it is important to preserve original layers naming on export.

Possible Workflow 2:
Export EXR render from 3D editor -> Import to PhotoLine and edit -> Save as PLD.
In this case it would be perfect to preserve original EXR compression inside PLD file, but unfortunately PhotoLine can't do it yet. EXR saved to PLD always re-compressed and PLD file size always became 2-3 times more than original EXR with PIZ compression. This re-compression also take large amount of time.

Possible Workflow 3:
Create PLD -> Export to EXR -> Use in some other VFX/3D app.
In this case it might be useful to preserve original PLD layers structure in exported EXR file and use layers auto naming 1,2,3,4,5. It also might be useful to have an option to disable layers auto naming 1,2,3,4,5 and use only exact layers names, because user may add layers names specially for some VFX/3D app requirements.