Gather use cases for color metadata in OTIO.
Compile a set of user stories for specific use cases for color information modeled in otio.
Example:
- As an assistant editor I'd like CDL transforms to come into my NLE so that I can pass them along to VFX vendors
Completion of this ticket should result in:
- List of use cases OTIO should address
- Scoping of areas OTIO explicitly shouldn't address
- OTIO's relationship to other projects expressing color information (ACES, OpenColorIO, ASC CDL, etc.)
I’m writing a contrib adapter for Colourlab Ai. Our software provides automated color matching of multiple shots to a reference shot.
Colourlab Ai is generally used in combination with another NLE. For example, a user can “fetch” a DaVinci Resolve Studio timeline into Colourlab Ai, perform color matching, and then “sync” the grade with the Resolve timeline. The user can then manually refine the synced grades for each shot.
The color and editorial metadata is serialized into JSON and exchanged between the applications. We see a value in providing third parties a method for exchanging this metadata using OTIO instead of directly reading and writing our JSON format.
OTIO to Colourlab Ai, the minimum required set of color metadata:
- ISO
- White Point
- Tint
Colourlab Ai to OTIO, the minimum required set of color metadata:
- 3D LUT path
- CDL