Recap:
- Talked about PR for the reference implementations in applications for temporary use.
- Feedback welcome
- Should we enable ACEScc as a working space along with ACEScg and ACEScct? Group says not necessary.
- @sdyer: we should update the main readme as well
- Talked about the PR for updating the naming conventions on the CTL
- @sdyer : didn’t take it too far with the inverse separation, so if anyone has opinions, let us know
- URN versioning updates:
- a1.3.0 → a1.1.0
- Options: a1.v1 - this is the proposed new versioning schema Scott is likely to propose in a revision to the current naming/version doc
- Group likes a1.v1
- Talked through the User Guide a bit
- @jzp : make sure the same consideration is given to each dept, and not just finishing and VFX
- @matthias.scharfenber : yes, and around 3D LUTs - one of the open questions is should we “bless” a shaper function to accompany the work for the cases where folks need to bake a LUT based on ACEScct vs a camera vendor encoding?
- Group agreed that we should provide information around the issues, but not a solution, as once the algorithm is properly implemented in all software, it should not be necessary.