Skip to main content
Participant
July 17, 2026

app.project.workingSpace and AEGP_SetWorkingColorSpace do not clearly support OCIO working color space names

  • July 17, 2026
  • 0 replies
  • 4 views

We use OCIO color management in AE 26.3, but we have run into a limitation where the existing API setters for the Project Working Color Space still seem to rely on the legacy ICC workflow.

Currently, we can successfully query the active OCIO space, but we are unable to set it programmatically:

  • JSX: app.project.workingSpace currently only accepts legacy ICC profile description strings. When the project's Color Engine is set to "OCIO Color Managed", trying to pass an OCIO color space to this property fails.

  • C++ SDK: AEGP_UtilitySuite6 provides AEGP_GetOCIOWorkingColorSpace to read the active space as a string, but the available setter AEGP_SetWorkingColorSpace strictly expects an AEGP_ConstColorProfileP (ICC profile pointer). There doesn't seem to be a symmetrical way to pass an OCIO string back into the system.

Our Request: Could you please consider updating both the JSX and C++ APIs to support OCIO setters?

Thank you for your time and help!