NEW VWG! Notice of Meeting - ACES Gamut Compression Implementation VWG - Meeting #1 - 4/1/2021

ACES Gamut Compression Implementation VWG Meeting #1

Thursday, April 1, 2021
9:30am - 10:30am Pacific Time (UTC-4:30pm Friday)

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

  • April 8: 5-6pm PT
  • April 15: 9:30-10:30am PT
  • April 22: 5-6pm PT
  • April 29: 9:30-10: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

Meeting Recap:

  • Started by reviewing the Implementation group proposal
  • Starting at the beginning - talking about on-set workflows:
    • Should the compression be on by default? A few folks agree - @ptr , @daniele, @KevinJW, @Giardiello
    • Do we enforce order of operations? Allow more than one application?
  • @ptr - two approaches on set
      1. Track compression as you do cdls, in the AMF so you can exactly recreate
      1. A totally local and temporarily enabled thing - is there a reason to pass it on? Is it just a safety on set?
    • If you’re baking it into dailies, you definitely need to track it
  • @jzp : 1 - once the fix is applied, usually that’s enough, you don’t often need it again. On set, if someone sees a problem, it must be fixed - turn it on, and never see the problem again. Therefore, it needs tracked.
  • @Giardiello - huge benefit to having it always on for preview on set. Only edge cases would have it off.
  • @joseph brought up hardware correction vs. software - we need to be specific about the intended workflow
  • @nick - this is a scene referred fix. It should never be applied in a display-referred space
  • @joseph - scene-referred transforms in monitor are a distinct possibility, in the future
  • @ptr - monitoring shouldn’t be an issue, if you’re in an ACES workflow, monitor is usually in PQ and not sending log over the wire
  • @joseph - we should add it to workflow docs as edge cases
  • For VFX:
    • @KevinJW: many many things change the color on a vfx shot (despill, tech grades, etc), do we care? Is it worth tracking?
  • @jzp - VFX pulls should not have it baked in. This should be applied in the working space, not before. ACEScg ACEScct only.
  • @Giardiello - on dailies - used it on a few shows. Ended up putting it always on because it’s hard to track. But if it was trackable via AMF, might change his mind.
  • @joseph - what about loadable on-camera LUT for shoots without a DIT
    • Do we need to track this? Did not reach a consensus here

Recording & Transcript