-
Notifications
You must be signed in to change notification settings - Fork 36
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
AVX Parameter - Info #124
Comments
Plugins can have private binary blobs of binary data as parameters. You will probably need to reverse what all the bytes in the blob represent. Feel free to document it here if figure it out. |
Has anyone figured out this yet or have any information from docs for AVX that might be useful ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Mark,
I am using pyaaf2 to help automate imports in Avid Media Composer. I'm trying to generate sequences that contain Avid Subcap effects.
These are defined within OperationGroups with Parameters. The Subcap text is stored for instance in a property_entry called Caption. This looks to be some kind of structure. All I've managed to parse really is that from byte 53 there's a length int encoded in the bytes, followed by an ASCII encoded string (length defined by the previous bytes).
I don't see anywhere in PYAAF2 to decode this, but am I missing it?
If not, do you know anything about how these AVX parameters are defined in an AAF file?
The text was updated successfully, but these errors were encountered: