2021-04-13

Owned by Michael Dolan
Apr 19, 2021
3 min read

04 13, 2021

Host: Michael Dolan

Attendees: 

Michael Dolan (TSC Chair) - Epic Games
Carol Payne (TSC) - Netflix
Doug Walker (TSC Chief Architect) - Autodesk
Christophe Brejon
Kevin Wheatley (TSC) - Framestore
Thomas Mansencal - Weta Digital
Mark Boorer (TSC) - Industrial Light & Magic
J Schulte - Industrial Light & Magic

OCIO Config Working Group Meeting Notes

  • Reference config status:

    • 0.1.0 release is available: https://github.com/AcademySoftwareFoundation/OpenColorIO-Config-ACES/releases/tag/v0.1.0

    • Doug: How should we publish/announce that?

    • Thomas: Everywhere, but with caveat that it's just for developers. Release includes notes and config. Also has note on intended usage in config description.

    • Carol: Can bring up in next TSC meeting too, and to Academy.

    • Doug: Should we do post on ACES central?

    • Carol: People will be excited.

    • Michael: Probably ok to share widely, but with big disclaimer about intended use.

    • Thomas: There will be user issues, so more for experts to play with.

    • Doug: Interesting to get feedback from Nuke alpha.

    • Mark B: Currently combines all displays in Nuke. New option to not include roles in menu which is nice.

    • Doug: Should ordering in config be what app uses?

    • Kevin: Yes. I rely on that in config design.

    • Mark B: Tend to rely on first color space in list, but less on other order.

    • Thomas: Will need to do PR to use latest aces-dev.

    • Michael: Are we putting ACES version in config?

    • Thomas: We can put commit hash in there.

  • Rendering config:

    • Doug: Use case is for DCCs to use when customers aren't working with input images. Just creating images and don't want to deal with color management. Want linear space, but don't need IDTs.

    • Thomas: Yes, agree. I built one for team based on ACES config with removed camera spaces and most views. Spaces to interchange with sRGB.

    • Carol: Maybe call it CG or animation config instead of rendering config.

    • Group agrees. CG.

    • Thomas: Think intent is to make original v1 config less gnarly for people. For users not concerned with cameras.

    • Christophe: List created on ACES central. Guerilla render wants to ship with this config.

    • TODO: Christophe will work on CG config proposal spreadsheet.

    • Michael: Small but will likely be most widely used config.

    • Thomas: Looking at API for how to do this in generation code; much easier to work with v2 to massage config.

  • Studio config proposal:

    • Spreadsheet: https://docs.google.com/spreadsheets/d/1nE95DEVtxtEkcIEaJk0WekyEH0Rcs8z_3fdwUtqP8V4/edit?usp=sharing

    • Michael: I added a column for tracking status with camera vendors.

    • Thomas: When reaching camera vendors, should reach out with Academy. More credibility for our request.

    • Carol: Once we decide who to contact, I can reach out with the Academy. Hopefully most won't be an issue.

    • TODO: Carol will contact camera vendors with Academy.

    • Mark B: Need to add aliases for new spaces.

    • Michael: Goal to have this list complete by next meeting to formalize our proposal.

    • Doug: Should we add AP1 primaries with gamma for 8-bit storage. Not advocating for it, but saw thread related to MaterialX on this. Anyone think worth adding?

    • Thomas: If it will help someone out, ok with it.

    • J: Concern is that the generic config was massive with multiple versions. Are we going to end up there again? May not want to carry everything over.

    • Kevin: We do AP1 with sRGB curve. The only weird one.

    • Doug: Think we should leave them out unless someone asks for them.

    • Thomas: Think the risk for putting them in there is they become standard and have to support them.

    • J: Is there a specific target audience for this config? Very wide use case. May not be possible to work for them all.

    • Michael: The config is intended for studios that don't have dedicated color scientist, and as a starting point for studios that do. Example of end-to-end studio color pipeline. Simple to make subset and superset configs or other variations, like the CG config which was recently proposed.

    • Thomas: In future would like to have generator online to generate configs with these. What I'm envisioning for less tech savvy users, to build tailored config.

    • TODO: Michael will share proposals in Slack for feedback.

  • Items for next meeting agenda:

    • Finalize CG and studio config proposals.