Blender Support for ACES (Academy Color Encoding System)

Archive User Feedback
,
201

Hi all,

Now that Blender 3.2 beta is out with default support for ACEScg input transform/openexr baking (note it is different from previous Linear ACES, which assumes ACES2065-1 color space), I have some follow up questions:

  • Without adding OpenColorIO profiles, Blender itself still use linear rec.709 (sRGB) as working space by default, right?

  • Even if we added the OpenColorIO profiles, how do we know whether we are using ACES workflow? By setting the “Display Device”, have we actually changed the working color space in Blender? Or have we only changed the so-called output transform (RRT+ODT)?

  • Even if we can set the working space correctly, how do we know the final output transform is using the default ACES gamut mapping and tone mapping? This is the “View Transform” and “Look” option as I understand, but how do we find an option that can match with other applications? Say for example, a game engine using ACES tone mapping (which is likely using an approximation due to performance reasons.) Do I basically had to sync these OCIO profiles to every applications for consistency?

  • In short, what do we actually get by adding OCIO profiles to Blender 3.2 at this point?

1 Like