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

Embed External MXF vs. Link External MXF #138

Open
ndeshpande2022 opened this issue Oct 18, 2024 · 0 comments
Open

Embed External MXF vs. Link External MXF #138

ndeshpande2022 opened this issue Oct 18, 2024 · 0 comments

Comments

@ndeshpande2022
Copy link

Hi there,

We're using PyAAF2 to link external MXF Files with 608/708 closed caption data. One thing we've found is that even after linking, we still need to keep the MXF file around. We're guessing this is because the MXF file is linked instead of being embedded.

Our question is if it's possible to embed the MXF file into the AAF instead of just linking.

Our current code for linking looks like this:

from __future__ import (
    unicode_literals,
    absolute_import,
    print_function,
    division,
    )
import aaf2
import sys
import argparse

def main():
    parser = argparse.ArgumentParser(description='Link MXF file to AAF file.')
    parser.add_argument('input_file', help='Input MXF file')
    parser.add_argument('output_file', help='Output AAF file')
    args = parser.parse_args()

    with aaf2.open(args.output_file, 'w') as f:
        for mob in f.content.link_external_mxf(args.input_file):
            print(mob.name)

if __name__ == "__main__":
    main()
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