Notice of Meeting - ACES Gamut Mapping VWG - Meeting #28 - 9/10/2020

ACES Gamut Mapping VWG Meeting #28

Thursday, September 10, 2020
9:30am - 10:30am Pacific Time (UTC-4:30pm Friday)

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

  • 9/17/20, 5pm
  • 9/24/20, 9:30am

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


  • @matthias.scharfenber noted that the nuke script in the research folder to calculate the distance limits/threshold is still the old CC24 values - but the difference is minuscule so should not really affect anything.
  • @sdyer has the update removing the clamp on the AP0 to ACEScg CTL in his fork of the repo, and has filed a bug report so it’s tracked and will figure out how to get to released
  • @KevinJW - for the distance calculations, may be helpful to instead of looking at the boundaries - look at the intersections, and use that to calculate the inverse
  • Around the current default of 1.2 for the power compression value: @jedsmith notes that 1.0 is reinhard, and values higher than that tend towards C2 continuity. So 1.2 was a default picked subjectively.
  • Half-float quantization could be used to start, and subjective tests from there. @nick suggested a high/medium/low “aggressiveness” exposed to the user.
  • Blue-screen test shoots:
    • Highly saturated object - in and out of focus
    • Glass bottle
    • Reflective things: safety vest/jacket, bike reflector, tin foil
    • Light trap
    • Emissive light (lens flares?)
  • @jedsmith asked whether using the max of the vendor gamuts makes sense, instead of possibly taking an average of the out of gamut values from the test imagery (reasoning being those examples were put up as extreme examples). @matthias.scharfenber pointed out that it gets slightly subjective, and also work might be done in the camera encoding primaries and therefore might be needed. Consensus is to continue will camera encoding primaries in testing and go from there.
  • Can the algorithm be encapsulated in a 3d LUT? @matthias.scharfenber noted that the key is in the shaper function. You need to encapsulate the negative values. Possible to use a reflected ACEScct curve.

Recording and Transcript

Code snapshot