ACES 2.0 Meta Framework


as promised here is a document gathering thoughts about a possible future for the ACES project in terms of a modular meta-framework.
It is short but I hope still valuable.

Proposal_ACES_Next_Metaframe.pdf (908.9 KB)


Über-CMS <3

No surprise but excellent to see that written @daniele! I only wish it came last week as some of those points were discussed during TAC this morning but not to the extent they should have been. It is certainly worth re-raising to Arch. TAC specifically. There are good points made and it would be a shame not doing it.



Very interesting. Thanks Daniele !

This idea of “meta framework” or modularity was discussed during the last TAC meeting (here is a link to the recording) and it would have been great to have these slides for better illustration.

The terminology explanation about Color Management System and Color Management Workflow is quite enlightening to say the least.

Hopefully it can be discussed in a more precise way next time,


Some Pro and Cons of the proposal (of course not complete):

Starting with the Cons:

  • it is a lot, a lot of work!
  • it needs to revisit some of the most fundamental definitions, some examples:
    • reference scene
    • reference display(s)
    • reference observer
    • specifying display linear
      • Relative black vs absolute
  • it needs some new definitions
    • defining viewing conditions
    • defining the concept of display rendering transforms


  • useful to modernise the assumptions and definitions which are already a few years old (things have changed)
  • makes ACES adoption much easier
  • the default implementation can be tailored more towards the novice and intermediate user because expert users can customise
  • improves the current archive situation
  • more creative freedom
  • tailored shows can maximise the value of the show
  • encourage innovation
  • ACES becomes agile and can be adapted quickly to changing requirements
  • the vanilla ACES LiveCycle is decoupled from the vendors’ implementation
  • no additional complexity for vanilla ACES shows (Metadata-driven only if you want to depart from vanilla ACES)
  • refactoring the pipeline helps to design a better vanilla output transform.