Summary here, sorry for the delay:
- We started the meeting revisiting testing procedures, and some test operations were defined but need fleshing out:
- Filter, key, degrain, alpha blending, legacy blending modes (display referred), blurs/spatial operations
- @joseph suggests a visualizer to show what is outside the safety zone in an image as an aid for testing
- It was brought up that special attention needs to be paid to workflows for animation and motion graphics where super saturated colors are common and desirable, and Kevin pointed out that motion graphics are not always sRGB these days, they’re often P3. We don’t want to make life harder than it already is to bring these elements into a workable ACES space.
- Most of the discussion (there was a lot of back and forth, please watch the recording for full detail) revolved around implementation of the algorithm - where and how it should fit into the pipeline. There are basically two (it’s a bit more nuanced, but for the sake of discussion) options:
- Include the gamut mapping algorithm as a part of every AP0 to AP1 colorspace transform
- Create a separate additional operator for the gamut mapping algorithm, and define pipeline constraints (such as usage via AMF) to aid users in production application
- We acknowledge that there is a lot to unpack and test here, and therefore suggest the start of a pro/con list in writing to facilitate further discussion. We will create another ACES central post in that vein, and a slot on the Dropbox paper so we’re all working on the same thing.
- @joseph shared the ARRI workflow diagrams as a visual aid to discuss the position of the transform: https://www.arri.com/en/learn-help/learn-help-camera-system/camera-workflow/image-science/aces/post-production