Multilayer EXR render splits RGB channels

[MT_mm]

Hi.

Can not load in RGBA as unique channel. I render the multilayer EXR file throng C4D octane render. Any help would be appreciated. 

Thanks.test0000.exr

[NotMyFault]

Hi,

This is not a bug, it works as designed and documented.

https://affinity.help/photo/English.lproj/pages/HDR/openexr.html

Multichannel import:

• Each channel is imported to a discrete layer in the Layers panel.

• Each layer retains its affix (e.g., .RGBA, .XYZ).

• Layers can be hidden or shown and edited individually.

How you can work with these files in Photo:

1. To merge the individual color channels into one RGB image, you can:

• add an channel mixer adjustment to each channel, knocking out all but one color channel
  • so for red:
    • red channel at 100% red, rest 0%
    • green channel all at 0%
    • blue channel all at 0%
• and set blend mode to "add" for the pixel layers.
• Example for one layer:
  

2. For further processing, please visit the tutorial. Just skip the "new stack" as your layers are already in one document.

 

Edited June 1, 2021 by NotMyFault
corrections

[MT_mm]

Hi, @NotMyFault

Thank you very much for your answer.💯.I think that when importing multi exr files, there is a dialog box to choose whether to merge layers has same name is better.

[Chris B]

Hey MT_mm,

This is currently by deisgn. Though I do agree it could be a worthwhile feature request. Other apps let the user decide what channels to use etc. 

[Mike_A]

If this is 'by design',  it suggests those who are doing the designing have no idea how these files are intended to be used.

[Mike_A]

MT-mm,

If you're still following this ... I had a similar issue, see:

However, after a bit more testing - read down the thread to 'important update' -  it looks likely that the issue is EXRs saved from C4Ds multi-pass system. Other exrs I've tried import into AP as expected - as RGB layers.

I use Redshift and that has an alternative ' direct' saving mechanism which avoids this issue. I've no idea if Octane has something similar.

So:

This is seems to be a glitch somewhere on the C4D - AP axis.

It isn't 'by design'.