-
Notifications
You must be signed in to change notification settings - Fork 294
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
AAF adapter #198
AAF adapter #198
Conversation
This is a work-in-progress towards addressing #1 |
60f1c33
to
75de009
Compare
For people who would like to test this, there are prebuilt pyaaf1 wheels here of the latest version for mac and windows users. |
Thanks @markreidvfx, and congrats on the 1.0.0 of pyaaf! |
@jminor staying at the head is preferred. I try and do a release every time I merge the dev branch into master. Even though I've been more focused on pyaaf2, I will try and keep pyaaf1 maintained for people using it. |
Thanks @markreidvfx. We'll keep our master branch on the head of pyaaf1. However, when we do a release of OTIO, it probably makes sense to pin that to the current release of pyaaf1 at the time of the release. |
Turned off lots of debugging print statements.
… (only remove them from Stacks).
…range and in_offset/out_offset.
…identical to how Avid Media Composer flattens.
Landing this onto the AAF_adapter branch, so we can continue development there before landing to master. |
Here's a starting point for reading AAF compositions into OTIO.
As it stands, it can read a multitrack AAF composition, including Filler, SourceClips, Transitions and custom bin column metadata.
It does not yet support markers, nested compositions, any sort of effects, audio tracks, or a million other things.