Skip to content
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

Converted otio file requires Load Media Database to bring media online in Media Composer #52

Open
peter-targett opened this issue Oct 31, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@peter-targett
Copy link

peter-targett commented Oct 31, 2024

Bug Report

This could be an issue with Media Composer but otherwise it could be resolved in the generated AAF when converting from a .otio file that has in this case an MXF file and the required Source ID in the metadata, to ensure the media is linked and online when imported into Media Composer.

To Reproduce

  1. Operating System, macOS.
  2. Python version 3.9.
  3. OpenTimelineIO release version 0.17
  4. Run otioconvert -o input.otio -o output.aaf, with:

input.otio

Cannot include the sample media but any MXF file with the correct Source ID added to the otio file will reproduce.

Expected Behaviour

Media is linked in Media Composer, without needing to do File > Media > Load Media Database to trigger it online.

@peter-targett peter-targett added the bug Something isn't working label Oct 31, 2024
@jminor
Copy link
Member

jminor commented Oct 31, 2024

@peter-targett
Copy link
Author

I'm using this advice to make sure the Source ID is written into the AAF, what I'm trying to do is not depend on an AAF to start with but export an AAF without any prior AAF as a starting point. I used otioconvert to make a .otio from the Avid re-exported AAF, the otio file contains metadata from the AAF but I don't think this will help in the first case. I wonder if this is somehow related to the changes here. I'm examining the axdump text output between the pre-load-media-database and post AAFs from Avid, they are different.

@peter-targett
Copy link
Author

Just noting the initial differences between the AAF (axDump) before on left and after Load Media Database right:

AAF-diff-1 AAF-diff-2

@markreidvfx
Copy link
Member

markreidvfx commented Nov 18, 2024

This sounds like a Media Composer issue. What version of MC is this? Does closing an re-opening the bin also work?
It could be related to this issue
markreidvfx/pyaaf2#68

I never really dug too deep into it as I don't use AMA/Media linking much.

The diff image looks like TimelineSlot->SourceClip vs TimelineSlot->Sequence->SourceClip both of which should be valid

@peter-targett
Copy link
Author

peter-targett commented Nov 18, 2024

This sounds like a Media Composer issue. What version of MC is this?

24.10.0.58607 (macOS)

Does closing an re-opening the bin also work?

No, this didn't trigger the media online either. The below issue does seem related though:

It could be related to this issue markreidvfx/pyaaf2#68

@peter-targett
Copy link
Author

This sounds like a Media Composer issue.
I never really dug too deep into it as I don't use AMA/Media linking much.

The diff image looks like TimelineSlot->SourceClip vs TimelineSlot->Sequence->SourceClip both of which should be valid

I will also make contract with Avid to see if they can help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants