ACES Community Members,
Today we are happy to announce the release of ACES 1.3 : it includes new features and enhancements that fulfill the ACES 1.0 vision and sets the stage for ACES 2.0 development. Key new features and enhancements include:
- A new gamut compression algorithm to deal with the “blue fringe problem” some users experienced with extremely bright saturated objects (e.g. brightly colored LED lights).
- A minor update to the ACES Metadata File (AMF) to make it more flexible for production workflows.
- A color space conversion transforms (ACEScsc) for supporting the Sony Venice
- Minor bug fixes and documentation improvements (including moving the documentation to its own git repo for more development flexibility)
ACES 1.3 is a “minor” system release. This means the update does not change the Reference Rendering Transform (RRT) or modify the existing core transforms beyond addressing reported bugs and/or inconsequential formatting/whitespace changes. It also means the system will continue to be referred to ACES as “ACES version 1” in conversation and documentation.
With this release we are following a previously announced plan to ‘unbundle’ the ACES transforms from documentation and toolsets to further clarify ACES versioning. Documentation and toolset components will be released as they are available and announced separately, avoiding the need to be unnecessarily held up for a new release of ACES transforms.
Finally, this release is ready to be integrated into products. Releases of the ACES reference implementation are primarily targeted to ACES Product Partners and other manufacturers. To enjoy these new benefits, end-users should request that their preferred production and postproduction tools integrate these new features and fixes, as quickly as possible.
ACES 1.3 details:
Notes on the gamut compression transform
The gamut compression transform is the result of the work of the Gamut Mapping Working Group, to create a more robust solution to issues with out of gamut colors and the resulting artifacts (loss of texture, intensification of color fringes). The delivered gamut compression transform performs well with wide gamut, high dynamic range, scene referred content and is robust and invertible.
The gamut compression replaces the simple and less robust
LMT.Academy.BlueLightArtifactFix.ctl. The ACES gamut compression transform has numerous advantages over the BlueLightArtifactFix LMT. In particular, the gamut compression transform avoids changing colors that are well inside the destination gamut. Only colors that are out of gamut or very near the gamut boundary are affected.
As of this release, the Gamut Compression Implementation Working Group is working to provide recommendations and guidance to vendors to implement this transform directly their in products.
For those looking for more detail, the Gamut Mapping Working Group delivered a report to accompany the technical deliverable.
Notes on the updated AMF specification
ACES 1.2 included the release of the Academy Metadata Format (AMF) specification. Since that time a working group has been formed to provide guidance to vendors on the implementation of AMF into products and end-user guidance on production usage. In the process of testing and working with the initial specification, the group suggested extensions to the AMF specification to make it more useful in meeting specific use cases. ACES 1.3 includes an updated AMF specification and associated schema that allow all transforms to now be referenced by UUID, relative file path, or TransformID.
We would like to thank the members of the ACES community who have actively participated in the development of ACES 1.3 through ACESCentral.com and within the various Virtual Working Groups. We believe, through their participation in the development process, the result is a stronger ACES release that better addresses the needs of the motion picture, television and broader content creation communities.
Please check ACESCentral.com and the ACES Twitter and Facebook feeds for the announcement of an upcoming webinar where we’ll be discussing this release in more detail and you can ask questions about how this impacts you (in a positive way, we hope) as an ACES end-user or implementer.
With much appreciation,