how to set up correct aces settings between H20 and AE 2024?

I rendered one explosion effect in acescg color space(karma xpu/exr format),but i can't get the same result in AE 2024.The color difference is huge.

You forgot to change exr to acescg.

Why bother trying to match the settings? Point them to the same config file.

jsmack
You forgot to change exr to acescg.

Why bother trying to match the settings? Point them to the same config file.

I don't think so.I tested the settings you said,nothing changed.

Commenting so I can follow. I have the same problem, the EXR file from Karma is in .srgb I can not get to get the EXR in ACESCG space color :/

If you right click on the EXR and select Interpret Footage > Main is it set to ACEScg?

BrianHanke
If you right click on the EXR and select Interpret Footage > Main is it set to ACEScg?

Image Not Found

Yes,it is.The color is much red than H Mplay.

Strange. I just did a quick render to disk with Karma and it displays correctly in AE. I'm using my own OCIO config (which is pretty much the same as the official "CG" one). https://github.com/BrianHanke/bhgc_v2.ocio/releases [github.com]

wanglifu

BrianHanke
If you right click on the EXR and select Interpret Footage > Main is it set to ACEScg?

Image Not Found

Yes,it is.The color is much red than H Mplay.

did you rerender after fixing the config? The exr might be rec709 linear if not

jsmack

wanglifu

BrianHanke
If you right click on the EXR and select Interpret Footage > Main is it set to ACEScg?

Image Not Found

Yes,it is.The color is much red than H Mplay.

did you rerender after fixing the config? The exr might be rec709 linear if not

Yes,i tested it.But i don't think we should change the config,it's about the input exr colorspace,not output.Maybe i'm wrong.

Can you share a pic showing the difference between the Solaris viewport/MPlay and AE?

BrianHanke
Can you share a pic showing the difference between the Solaris viewport/MPlay and AE?

wanglifu
Yes,i tested it.But i don't think we should change the config,it's about the input exr colorspace,not output.Maybe i'm wrong.

That rule covers both input and output, but maybe doesn't affect karma/mantra output (not sure about that), just when saving with mplay

I just tested this with your exact setup, the default Houdini OCIO config and the AE CG config, using a pyro scene. I'm also getting different colors now.

Update: tested Nuke too, AE and Nuke match, Solaris viewport is the odd one out. Now that I think more about this I vaguely remember somebody telling me there was a long standing issue with the Houdini viewport clamping colors or something along those lines. That would explain why I notice a difference with pyro with many color values above 1, whereas my first test scene was all below 1.

BrianHanke
Update: tested Nuke too, AE and Nuke match, Solaris viewport is the odd one out. Now that I think more about this I vaguely remember somebody telling me there was a long standing issue with the Houdini viewport clamping colors or something along those lines. That would explain why I notice a difference with pyro with many color values above 1, whereas my first test scene was all below 1.

Nuke and houdini match for me. Are you sure you have the same config and display-view between both?

BrianHanke
I just tested this with your exact setup, the default Houdini OCIO config and the AE CG config, using a pyro scene. I'm also getting different colors now.

The default Houdini config isn't ACES

Hmm. I'm talking about the "factory default" Houdini 20 config: .../packages/ocio/houdini-config-v1.0.0_aces-v1.3_ocio-v2.1.ocio. (Has "aces" in the name.)

I do notice that in that one scene-linear is Rec.709 while scene-linear in the "CG" one that comes with After Effects is ACEScg. In wanglifu's original screenshots he shows using the Houdini config and the AE CG one, so that's why I tested that.

I also notice that if you use the new Houdini OCIO menu the Render Working Space change doesn't "stick." Maybe that's the problem here? The OP shows he set it to ACEScg, but if I do that then it goes back to Rec.709 after reopening the menu.

Anyway, it seems like the source of the issue is using two different configs. Should just set a system-wide OCIO variable and keep things simple.

BrianHanke
Hmm. I'm talking about the "factory default" Houdini 20 config: .../packages/ocio/houdini-config-v1.0.0_aces-v1.3_ocio-v2.1.ocio. (Has "aces" in the name.)

I do notice that in that one scene-linear is Rec.709 while scene-linear in the "CG" one that comes with After Effects is ACEScg. In wanglifu's original screenshots he shows using the Houdini config and the AE CG one, so that's why I tested that.

Yes, that's why it's not ACES

BrianHanke
I also notice that if you use the new Houdini OCIO menu the Render Working Space change doesn't "stick." Maybe that's the problem here? The OP shows he set it to ACEScg, but if I do that then it goes back to Rec.709 after reopening the menu.

You have to save it and restart Houdini for it to stick.

jsmack

BrianHanke
Hmm. I'm talking about the "factory default" Houdini 20 config: .../packages/ocio/houdini-config-v1.0.0_aces-v1.3_ocio-v2.1.ocio. (Has "aces" in the name.)

I do notice that in that one scene-linear is Rec.709 while scene-linear in the "CG" one that comes with After Effects is ACEScg. In wanglifu's original screenshots he shows using the Houdini config and the AE CG one, so that's why I tested that.

Yes, that's why it's not ACES

BrianHanke
I also notice that if you use the new Houdini OCIO menu the Render Working Space change doesn't "stick." Maybe that's the problem here? The OP shows he set it to ACEScg, but if I do that then it goes back to Rec.709 after reopening the menu.

You have to save it and restart Houdini for it to stick.

Thanks!