August 31, 2021
Host: Michael Dolan
Attendees:
- Carol Payne (TSC) - Netflix
- Doug Walker (TSC Chief Architect) - Autodesk
-
Michael Dolan (TSC Chair) - Epic Games
- Thomas Mansencal - Weta Digital
- Kevin Wheatley (TSC) - Framestore
- Chris Brejon
- Zach Lewis - Method
...
- PR #31:
- Thomas: Mostly cleanup, NamedTransforms, aliases, and ability to pass existing config to config definition (really useful). Using this at work now.
- Carol: Example would be really helpful as well. Happy to help update docs.
- Michael: Remaining open item for CG config is CLF files.
- Doug: Will work on this.
- Thomas: Also need to add builtin support in addition to CLF. Some transform expressible as OCIO builtins. Currently CG config doesn't support that; only modified reference config.
- Michael: Will that be another CSV column or option?
- Thomas: Yes. PR in progress. Will do this for next time.
- CLF Format:
- Discussion of document: https://docs.google.com/document/d/1uYNnq1IlKqP8fRXnPviZHrAAu37ctvVsjJZeajOFF2A/edit?usp=sharing
- TODO: Talk to Sean and Joseph at ARRI and Graeme at RED for feedback on doc and approach.
- TODO: Carol will compile list of camera vendor contacts
- OCIO 2.1 config version change:
- Doug: We're releasing OCIO 2.1 today. Incrementing config version number for new versions, to include gamut compression transform. By default you will get the current version when creating new config. There are no 2.1 apps yet, and app with 2.0 will complain that it's for a future version. If writing config via python, need to manually set the version to 2.0 before writing it out. A consistency check will verify newer features aren't used. Not anticipating 2.1 apps until next year some time, so we'll initially be creating 2.0 configs, but we have version of config generator that includes the gamut compression transform, so will need to be 2.1.
- Thomas: PR has been merged, so is 2.1 now. Should We should indicate which are available for which OCIO version. Need to support OCIO version in generator explicitly. Perhaps we should prioritize this since it's broken for 2.0 now.
- Michael: 2.1 and 2.0.2 will be available in PyPI, but 2.1 will be installed by default through pip.
- Thomas: Will need to require latest version.
- Doug: Need to manually set the version through method on Config class. You can even write a v1 config with library.
- Michael: Could put note in release notes for release.
- Zach: Will CTF still be version 2.0?
- Doug: CTF will also be 2.1. By default will write version based on features used. Would like to do that with config, but more complicated. Will create issue.
...