Skip to content

feat(color): Use inactive color spaces in the OCIO config - #5387

Open
brechtvl wants to merge 1 commit into
AcademySoftwareFoundation:mainfrom
brechtvl:color-interop-inactive
Open

feat(color): Use inactive color spaces in the OCIO config#5387
brechtvl wants to merge 1 commit into
AcademySoftwareFoundation:mainfrom
brechtvl:color-interop-inactive

Conversation

@brechtvl

Copy link
Copy Markdown
Contributor

Description

In older ACES configs, like v2.1.0 bundled with OpenColorIO 2.3, the display color spaces are inactive. This meant they could not be looked up or converted to, even when specifying their exact name.

Now include inactive color spaces in the list, and add isColorSpaceActive() to test if a colorspace is active. Inactive color spaces remain hidden from the user interface in iv.

Ref #4980

Tests

Test output now includes these inactive color spaces.

Checklist:

  • I have read the guidelines on contributions and code review procedures.
  • I have read the Policy on AI Coding Assistants
    and if I used AI coding assistants, I have an Assisted-by: TOOL / MODEL
    line in the pull request description above.
  • I have updated the documentation if my PR adds features or changes
    behavior.
  • I am sure that this PR's changes are tested in the testsuite.
  • I have run and passed the testsuite in CI before submitting the
    PR, by pushing the changes to my fork and seeing that the automated CI
    passed there. (Exceptions: If most tests pass and you can't figure out why
    the remaining ones fail, it's ok to submit the PR and ask for help. Or if
    any failures seem entirely unrelated to your change; sometimes things break
    on the GitHub runners.)
  • My code follows the prevailing code style of this project and I
    fixed any problems reported by the clang-format CI test.
  • If I added or modified a public C++ API call, I have also amended the
    corresponding Python bindings. If altering ImageBufAlgo functions, I also
    exposed the new functionality as oiiotool options.

…onfig

In older ACES configs, like v2.1.0 bundled with OpenColorIO 2.3, the
display color spaces are inactive. This meant they could not be looked
up or converted to, even when specifying their exact name.

Now include inactive color spaces in the list, and add
isColorSpaceActive() to test if a colorspace is active. Inactive color
spaces remain hidden from the user interface in iv.

Signed-off-by: Brecht Van Lommel <brecht@blender.org>

@lgritz lgritz left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lgritz

lgritz commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

LGTM, would like double check from @zachlewis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants