Notice of Meeting - ACES Gamut Compression Implementation VWG - Meeting #12 - 6/17/2021

ACES Gamut Compression Implementation VWG Meeting #12

Thursday, June 17, 2021
5:00pm - 6:00pm Pacific Time (12:00am Friday UTC)

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

  • 6/24/21: 9:30am 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

Sorry for the delay, I forgot to post this! Recap:

  • @michaelch - powers that be would like to push out the GC before AMF, should we include the parametric version?
  • Group says no, we should wait on the parameters and just use the DCTL for now
  • @jzp - we just need to plan for the interim plan before AMF is implemented
  • Group agrees that writing a User Guide in addition to an Implementation Guide makes sense - especially around what users shouldn’t do
  • @nick - is it easy enough to make sure the GC gets turned off when choosing the “flat pass” mode when in Resolve? @michaelch - yes, should be
  • So the “easy” part is ensuring it’s off for VFX pulls - but how do we handle the returns from VFX that have the compression baked in?
  • @matthias.scharfenber - prefer exr metadata / headers
  • @jzp - you can’t just easily add a header attribute to an openEXR - if it were fixed length like DPX, you could hack it, but it’s not ideal.
  • You can modify metadata in Nuke, it would need to be put into the Nuke OCIO transform and not native to OCIO
  • @jzp - if we don’t standardize it, someone else will - and there will be a million different ways
  • Are there other options besides EXR metadata or naming conventions for tracking the gamut compression in the interim? Not really.
  • @joseph : if you’re going to add exr metadata, get it added to the reference openEXR implementation.
  • @matthias.scharfenber - but this is a temporary solution - just until AMF is up and running everywhere.
  • @nick - but it will still need to be recognized in the archive long term, which could be a headache.

Recording & Transcript