Open vade opened 4 months ago
There are 2 main issues here.
The first is issue is transitions currently require additional AAF metadata to output correctly. This shouldn't be necessary. Sensible defaults for a transitions should be chosen if metadata is not supplied. Transitions are done differently in AAF compared to OTIO, its get really confusing quickly :p
The second issue is difference in frame rates between a clip and media_reference
. This is a little more tricky to deal with. Will need to investigate what media composer does for this. I believe it adds some kind of retime operation to keep the correct playback speed.
Thanks @markreidvfx - I understand about the former, the latter seems more pertinent to tackle.
Would it be helpful if I can find a round-about way of getting a viable AAF (perhaps OTIO -> Resolve -> AAF?)
I was curious if in cases with mixed frame rates / time bases if AAF requires a 'conform' retiming effect added vs it just working.
I also have some contacts at Avid I can ask. I'll send them this thread.
Thank you!
It should be a matter of creating some timelines with mixed framerate footage in Media Composer. Export AAF files of a few isolated cases and identify the structure. The audio frame rate differences is a little strange, I'm not entirely sure whats going on there.
I've only played around briefly with this project for the first time this weekend. The source media is missing things like embed timecode, so it took me a fair bit of time to relink everything with the free version of Resolve.
We could definitely look at the AAF Resolve generates for reference. I did think of doing that but haven't really dug into it.
Digging a little into this, all the rate changes on audio clips. The AAF exported from Resolve uses no effect to deal with the changes in edit_rate
between SourceClip references. Maye the validation check of the media_reference's rate compared to the sourclip's rate is over zealous.
This AAF imports into Media Composer, but has some errors. Exception: PMM_INSUFFICIENT_MEDIA
which normally mean a clip is short on media.
Here are some test files from Avid, each file has an AAF and OTIO file to test frame rates. Each file was linked into the 24FPS project and transcoded to the original framerate of the clip.
Archive.zip
Specs Below:
Avid Project: 24 FPS Clip 1: Cosmos 24 FPS Clip 2: Chimera 23.98 FPS Clip 3: Chimera 59.94 FPS
Let me know if you need anymore files, I'm happy to help out.
Attached is a cleaned up version of the Picchu Timeline Picchu_Clean_Timeline.zip
Bug Report
Incorrect Functionality and General Questions
Attempting to convert
https://dpel.aswf.io/aws-picchu-edit/
fails using both release OTIO and OTIO 0.17-dev and associated pluginsTo Reproduce
In a clean v-env or conda env, install OTIO:
Then run
otioconvert -i ~/Downloads/aws-picchu-edit-4096x2048.otioz -o ~/Downloads/aws-picchu-edit-4096x2048.aaf -O 'AAF' -A use_empty_mob_ids="True"
macOS 13.4
3.10.0
0.17.0.dev1
Expected Behavior
Successful AAF conversion
Description of the expected behavior.
Logs
otioconvert
which fails on transitions and timing:otiotool -i ~/Downloads/aws-picchu-edit-4096x2048/content.otio --remove-transitions -o ~/Downloads/aws-picchu-edit-4096x2048/content-no-transition.otio
(I did this on an unzipped otioz structure, just for clarity)
And then running otioconvert again removes the transition errors, but of course timing is still a concern:
Any insight is helpful!