Notice of Meeting - ACES Architecture Technical Advisory Council (TAC) - July 26, 2022

Please join us for the next meeting of the:
ACES Architecure Technical Advisory Council (ACES Architecture TAC)

The meeting will be led by the ACES Architecture TAC Chair/ACES Project Vice-Chair, Rod Bogart, and will take place on

Tuesday, July 26, 2022
1pm - 2:30pm PST (Los Angeles time)
Add to calendar (.ics)
(TAC Members should have already received an invite)

If you’re new to our meetings structure, please note the following:

  • TAC Meetings are open for observation by the general public on GoToMeeting (GTM)
  • TAC Meeting participation is for TAC members. Observer participation is at the discretion of the TAC Chair. (Please use the chat feature in GoToMeeting to log your comments)

Instructions for using GoToMeeting to join an ACES TAC Meeting

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 for observation.

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

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


Below is the agenda for the Architecture TAC meeting.


  • Call for other business
  • Discussion of community participation guidelines
  • Output Transforms Working Group progress report
  • Open discussion topics
    • Role of ACESproxy (or some integer encoding) in ACES 2.0
  • Preliminary discussion with ASWF

Recording and transcript

On the topic of ACEScct as a new ACES proxy - we use ACEScct as a 16bit integer format within Photoshop and similar applications. this is obviously Full range RGB [0-65535]. The only real downside has been the dynamic range represented by that encoding can result in images being “a bit flat” - but people get over that.

Adding any Video encoding - my vote would be to only specify a narrow range mapping for any video representation (HD SDI, Prores, DNxHR, H.264, etc etc etc) and be clear that if you make a TIFF or DPX or whatever it maps to full range - yes it is not transparent to convert between the two, yes you loose any over/undershoot.

But it is better than storing ACEScct into a 16 bit half float format… which is wrong in so many ways :slight_smile:


Just pointing out that AP1 might be too small for encoding camera material in an integer space as out of gamut colours cannot be maintained.
Might be ok for proxy workflows but hearing that it is considers as an online mezzanine integer format makes me worry.

1 Like

Ah yes, I should caveat we only use ACEScct when it is the intended grading space for the production, otherwise we might use a camera encoding space, etc for the reason Daniele outlines.