Thanks Scott. Would you say we should avoid using transforms added or modified to the repository after the 2.0 tag? If so, how would we go about doing this – I can’t see any version tags in the transform repositories so I’m not sure how to check out a 2.0 set. Are we always meant to wait for a point release in order to reference a transform? I’m still not sure what to put in my AMFs.
Not necessarily. A transform doesn’t need to be in the ACES repos to be “legal”. Transforms at the HEAD of one of the transform repositories are perfectly valid, as are transforms not even on the ACES repository – people make and use custom Input, Look, or Output transforms all the time.
The transform repositories are not versioned to allow for adding new transforms between system releases. See ** Reference Code - ACES Documentation**
No. (see above)
You can link transforms in your AMF using one of three clipIdTypes:
uuid: Schema documentation for aces:uuidfile: Schema documentation for aces:filetransformId: Schema documentation for aces:transformId