I've made a test render in C4D using Redshift. The render is stored as an EXR file with ACES-cg as the colorspace. When I import this render into After Effects and apply FNord's OCIO plugin everything works great. It's set up according to the instructions on the Redshift site: https://docs.redshift3d.com/display/RSDOCS/Compositing+with+ACES The image looks the same as in my C4D renderview. See below:
If I now take this same render and go the route of not letting OCIO do the work but rely on AE's own colormanagement the results are different.
I'm starting with a new project. Set my project settings as following:
I now import the render. It will look washed out as it is not being interpreted correctly yet. AE thinks it's in sRGB by default.
Under Interpret footage I assing the ACES-cg colorspace profile to the render.
I would expect the render that is now interpreted as an ACES-cg render to look the same as in my C4D renderviewer or using the OCIO plugin. Instead it looks like this:
The transfer curve seems to be different as the image is much brighter than what I would expect. The brightest parts are completely blown-out.
Where am I going wrong? Why is there a difference between the two methods? Is there a way using the built in colormanagent to get my render to look the same as it does in my C4D renderview?
Learn how you can use Color Managed Workflows in After effects. This is a practical After Effects guide which is a 2 part series: In Part 1, I will explore color managing in 4 different color spaces: Display, Log, Linearized, and ACES. I will show a workflow for each, how to set it up, what ...
you can see in the tutorial I posted how to deal with this. most of Ae's tools are designed to work in Display color space. so if you shift to ACES, there are workflows for getting expected behavior. you can use exposure effect with checking bypass linear conversion. if you want to use curves you could do that in log color space so go from linear to log - do the curves, then back to linear