Skip to content

Implement Texture Asset Color Space 1.1 revision#16

Open
doug-walker wants to merge 2 commits into
AcademySoftwareFoundation:mainfrom
doug-walker:walker/texture11
Open

Implement Texture Asset Color Space 1.1 revision#16
doug-walker wants to merge 2 commits into
AcademySoftwareFoundation:mainfrom
doug-walker:walker/texture11

Conversation

@doug-walker

@doug-walker doug-walker commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

The following updates are made:

  • Add a "bypass" interop ID following up on this proposal.
  • Add a "g24_rec709_scene" ID.
  • Use "Interop ID" rather than "Compact Name" to adopt the terminology used in later recommendations in the series. (That term had not been coined at the time the first version was written.)
  • Bump the version number of the specification to 1.1.
  • Add the interop ID and display color space recommendations to the references section.
  • Updated the config file to add the new color spaces and add the interop_id.
  • Add a revision history as Annex E.

The addition of "g24_rec709_scene" is to respond to the fact that it has recently been added to OpenUSD.

While not currently listed as one of the allowed MaterialX color spaces on the main documentation page, "rec709_display" (which is mathematically equivalent) does appear in other areas of the documentation and historically was one of the allowed color spaces. It is currently supported by both the MaterialX default color manager and OCIO color manager (if using the built-in OCIO configs, which already contain this color space). Hence, it will likely need to be supported indefinitely for backwards compatibility.

While a gamma 2.4 Rec.709 scene-referred space is not widely used, or even recommended, the fact that OpenUSD and MaterialX may produce files tagged with that, implies that it needs to be in the CIF recommendation since it will be an interop problem otherwise.

Please ignore the very minor changes to numeric matrix values in the OCIO config file. There were no substantive changes here, but the matrix coefficients are printed to double precision and so minor changes in the NumPy runtime that generates it causes occasional rounding differences in the last digit.

Signed-off-by: Doug Walker <doug.walker@autodesk.com>
Signed-off-by: Doug Walker <doug.walker@autodesk.com>

@meshula meshula left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This looks good to me.

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

Labels

None yet

Projects

Status: Later

Development

Successfully merging this pull request may close these issues.

2 participants