Added new example AMFs with official URNs for ACES 1.3 and 2.0#6
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Over the past year, AMF implementers have requested new sample AMFs to cover the range of possible pipelines for both ACES 1.3 and the new ACES 2.0 transforms.
These new sample AMFs were programmatically generated and validated against the XML schema, using offical ACES transform IDs / URNs from the recently published JSON registry.
They cover the following combinations:
*The IDT chosen was the
CSCforACEScctto avoid choosing a third-party manufacturer.*The ODT chosen was
Rec.709 BT.1886.For ACES 1.3, this resulted in 76 AMFs, and for ACES 2.0, this resulted in 81 AMFs, for a total of 157 AMFs.
This PR will likely be followed up with more edge cases (e.g. custom IDTs and LMTs, using inverse ODTs as the input, etc) depending on the needs of implementers. There may also be value in creating an "invalid" example AMF set in order to help catch common mistakes or errors.