Notice of Meeting - ACES Gamut Compression Implementation VWG - Meeting #7 - 5/13/2021

ACES Gamut Compression Implementation VWG Meeting #7

Thursday, May 13, 2021
9:30am - 10:30am Pacific Time (UTC-4:30pm)

Please join us for the next meeting of this virtual working group (VWG). Future meeting dates for this month include:

  • 5/20/21: 5:00 pm PT
  • 5/27/21: 9:30 am PT

Dropbox Paper link for this group:

We will be using the same GoToMeeting url and phone numbers as in previous groups.
You may join via computer/smartphone (preferred) which will allow you to see any presentations or documents that are shared or you can join using a telephone which will be an audio only experience.

Please note that meetings are recorded and transcribed and open to the public. By participating you are agreeing to the ACESCentral Virtual Working Group Participation Guidelines

Audio + Video
Please join my meeting from your computer, tablet or smartphone.

First GoToMeeting? Let’s do a quick system check:

Audio Only
You can also dial in using your phone.
Dial the closest number to your location and then follow the prompts to enter the access code.
United States: +1 (669) 224-3319
Access Code: 241-798-885

More phone numbers
Australia: +61 2 8355 1038
Austria: +43 7 2081 5337
Belgium: +32 28 93 7002
Canada: +1 (647) 497-9379
Denmark: +45 32 72 03 69
Finland: +358 923 17 0556
France: +33 170 950 590
Germany: +49 692 5736 7300
Ireland: +353 15 360 756
Italy: +39 0 230 57 81 80
Netherlands: +31 207 941 375
New Zealand: +64 9 913 2226
Norway: +47 21 93 37 37
Spain: +34 932 75 1230
Sweden: +46 853 527 818
Switzerland: +41 225 4599 60
United Kingdom: +44 330 221 0097


  • On OCIO 2.1 Implementation:
    • @KevinJW: definitely want a user-driven version, unsure how to do that with the proposed OCIO implementation
    • @matthias.scharfenber: The parameterized version should be provided by the prescribed application, as the ACES-labeled implementation in OCIO should be standardized
    • @nick: There should likely be a discussion between OCIO and Foundry etc - on whether or not to expose FixedFunctions to the user
    • @KevinJW : We’ll need some tests for the parameterized version too. What’s the spec? How do we define? What happens if I pass a smooth gradient, do I still have it?
    • @matthias.scharfenber: Quick unit tests should be enough for the standardized ACES version: forward, inverse, CPU and GPU.
  • How does an application meet requirements for the logo program for this algorithm?
  • @sdyer : reference images already exist for the gamut compress algo, the still life and the synthetic chart. Not sure if the inverse exists, will check. We can include other reference images if the group wants.
  • @michaelmaloney333 - everything eventually gets concatenated into a 3D LUT - both in onset box and as a viewing transform for VFX
  • @nick: two different tiers of validation in CLF - preview and finishing, could be valid here for implementation of the gamut compression algorithm as well
  • @jzp: Yes, differences between CPU/GPU small form errors might not mean an exact 0 diff match, and we’ll need to account for thresholds. Have we tried it through the CLF strawman? Might be interesting to try it.
  • @carolalynn: @ptr couldn’t make it today, but he’s working through an implementation in Livegrade, currently it’s a checkbox on the input. More discussion to be had on placement, checkbox vs layer/node in a stack.
  • @jzp : is LMT the right catch-all for all of this? Should there be another slot? Input LMT and output LMT?
  • @carolalynn: is there anything in the ACES specification that defines where an LMT must be applied now? As in post-most-work etc? I will find the notes from where this was discussed in the Architecture group. There we ultimately landed on not rocking the boat and sticking with LMT.
  • @Giardiello - if Livegrade exports an LMT in AMF based on a checkbox, how does downstream software handle that?
  • @KevinJW : how do you distinguish between baked in and not baked in to the exr?
  • @Alexander_Forsythe : AMF has an “APPLIED” flag in the xml per element - should work perfectly for this use case. This flag is in active pipelines, and different from archived pipelines.

Recording and Transcript