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
Pros:
- 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.