-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACES 1.3 Reference Gamut Compression URN incorrect #159
Comments
As of 2.0, the Reference Gamut Compression CTL lives in the aces-look repository: https://github.com/ampas/aces-look/tree/main/reference_gamut_compression I was unaware that they had included the URN in the documentation, which is now outdated. I will add that to the updates I have in progress to get documentation up-to-date with 2.0 changes. If it is necessary for your workflow with 1.3 transforms, I could go back and make a branch off of just before ACES 2 changes were merged in and tag it v1.3.1. |
Ah, yes, I see now that right after the 1.3 tag, this was cleaned up but no additional tag was made. I could push a 1.3.1 tag at d3d4df5 if its helpful for you. |
Oh, that would be quite helpful! Thanks for the help! |
In the Reference Gamut Compression CTL, the following URN is used:
urn:ampas:aces:transformId:v1.5:LMT.Academy.GamutCompress.a1.3.0
However, guidance to implementers has been to use:
urn:ampas:aces:transformId:v1.5:LMT.Academy.ReferenceGamutCompress.a1.v1.0
This unfortunately:
I suggest:
This allows tooling to walk the release tags and and discover the new preferred transform URN as well as make sure the git repo maintains a canonical truth of that URN existing.
While this particular issue should clear up with the migration to ACES 2.0 and the new ACES URN scheme, ACES 1.0 is still the system that the vast majority are running on and I think that this change is worthwhile because there is still some time before ACES 2.0 will become ubiquitous in show workflows. Additionally, having the preferred URN recorded in this git repo will aid in resolving in future archival cases.
The text was updated successfully, but these errors were encountered: