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

Create an MXF compatible with pyAAF2 #97

Open
ndeshpande2022 opened this issue Sep 17, 2024 · 1 comment
Open

Create an MXF compatible with pyAAF2 #97

ndeshpande2022 opened this issue Sep 17, 2024 · 1 comment

Comments

@ndeshpande2022
Copy link

Hi there,

We're using raw2bmx to generate MXF files with embedded 608/708 closed captioning. Unfortunately the MXF files are not compatible with pyAAF which we use to generate an AAF file for Avid Media Composer (with the MXF linked).

It looks like the issue is related to the fact pyAAF can only link OPAtom mxf files. I believe this is a simple fix in the MXF header and has to do with the Operational Pattern Item Designator: ({ 0D.01.02.01.01.01.01.00 })

I think it should be changed to { 0D.01.02.01.10.01.00.00 }

Which is what it is in other MXF files that work with pyAAF.
Not sure what else this may impact but I thought I would bring it to your attention in case someone else is trying to do the same thing.

@ndeshpande2022
Copy link
Author

I wanted to correct my original ticket. The issue does seem to be around the operation pattern.
raw2bmx generates an MXF with an operation pattern of: MXF OP1a SingleItem SinglePackage UniTrack Stream Internal - [ 060e2b34.04010101.0d010201.01010100 ]
image

However, pyAAF requires an operational pattern of MXF-OP Atom 1 Track N SourceClips - [ 060e2b34.04010102.0d010201.10010000 ]
image

It appears to be a very simple change to the bytes being added. I hope this helps everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant