2023-03-28

Owned by Carol Payne
Mar 28, 2023
2 min read

March 28, 2023

Host: Carol Payne

Secretary: Carol Payne

Attendees: 

Carol Payne (TSC Chair) - Netflix
Doug Walker (TSC Chief Architect) - Autodesk
Mark Titchener (TSC) - Foundry
Thomas Mansencal - WetaFX
Chris Davies



OCIO Config Working Group Meeting Notes

  • Modifying ACES configs, i.e. to add things specifically for Nuke

    • Thinking of adding a prepend or end to the name, as well as in the description, that the config was modified for specific use in Nuke, etc

    • Group agrees, and that it makes sense for nuke to only ship that, and not the default aces configs

    • Within that, about the texture_paint and matte_paint roles - any plans to switch that? Mark - yes, sensible defaults is part of this work too.

    • Using aliases in the short term to fix annoying mismatches, while we work on longer term solutions.

    • Looking at this across the foundry suite of products, not just in Nuke

    • Camera input spaces should error if not found, but other standards like gamma, etc can likely map okay

    • Also working on the display/view in the write nodes, should be coming soon

    • Chris Davies - does the order respect the order in active_views?

      • Mark - one big list in the viewer drop down right now, on the list to do

      • As far as order, a few bugs were fixed around active views and ordering, but let us know if things are still funky

      • Doug - there were some fixes in OCIOv2 that changed/fixed some things as well

    • Interesting topic for discussion: change management for ACES OCIO config updates vs. application updates/changes to the base config

      • Config merging feature could likely be of use here for sure

  • Chris: might want to add unique metadata to a colorspace, but don't want it to show up in UI - any advice?

    • Could put anything in a YAML comment, but wouldn't be accessible by the OCIO API.

    • Could use the metadata in a CLF/CTF file. It's another external file to track, but accessible and parseable in OCIOv2.

    • Otherwise, you're pretty much stuck with strings in the description, which will show up in tooltips, etc.