TSC Meeting Summary - April 14, 2026

Technical Steering Committee TSC Meeting Notes
1

Meeting Recap

This was the first of one of our working-group-focused TSC meetings. The meeting focused on two main topics:

  1. the development of a new Look Modification Transform (LMT) for
  2. discussions about versioning and transform ID management in the ACES repository

Reminder: TSC meetings are held every other week and are open to anyone. If you have a discussion topic, please try to let me know in advance so I can allot time on the agenda for it.
Calendar | Past meeting notes

For more detail, you can also review the full meeting notes (& access the recording).

Contrast LMT Discussion

On the Slack channel, Doug has provided an OCIO config containing some options for a proposed Contrast LMT and is seeking structured feedback from the community.

What is it: This LMT is intended to replace the “quick and dirty” sample LMT that had been included with the initial ACES 2 release as an example Look, but which did not produce acceptable results. The new transform aims to deliver a more useful and production-ready contrast look, aiming to add back a highlight shoulder (e.g. closer to ACES 1 contrast) while preserving the color reproduction differences in ACES 2.

Important context:
This is a look, not the look. It is not intended as a required transform, but rather as an example of a well-crafted, production-quality LMT designed for a specific use case.

The group discussed timeline considerations for finalizing the transform’s settings and incorporating into ACES so that OCIO can include in their fall release. We are looking for feedback on the chroma adjustment parameters.

More will be posted about this in a separate thread for visibility. [link TBD]

Versioning, Transform IDs, and Release Process Discussion

A separate discussion focused on improving how ACES updates are tracked and communicated. Historically, there has been a lack of clarity around:

  • What constitutes the “ground truth” version of ACES
  • When implementers should adopt updates
  • Which transforms are required vs optional

Proposed Improvements

  • Release Cadence

    • Move toward a predictable schedule (e.g., biannual releases)
    • Helps vendors align development and integration cycles

  • Automation & Tooling

    • Improve child → parent repo workflows - Leverage new Python tools for AMF and transform ID management to enchance automated updates to transforms.json and CHANGELOG
    • Solidify and communicate intended usage
    • Goal: improve transparency and maintainability of the transform registry