Latest post Tue, Jan 8 2019 3:17 PM by JamesTV. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • Tue, Dec 18 2018 2:10 PM

    • JamesTV
    • Not Ranked
    • Joined on Fri, Mar 31 2017
    • Posts 25
    • Points 305

    AAF Generation using AMT v3

    We are assessing the use of AMT v3 in our implementation - and are very keen to try and make use of the AAF generation capability that it includes. However, the example only supports a single file per AAF - which is a bit pointless as the whole idea for AAF is to connect multiple files and present them as a sequence.

    Is there any way to provide mutilple source OPAtoms into this AAF generator?

     

     AAFCreationOptions ()

            {

                this -> addArgument (Common::makeArgument ("Source MAD", "Source media asset description xml path", m_sourceMADPath, ArgumentRequired));

                this -> addArgument (Common::makeArgument ("Output AAF", "Output file where to write the resulting AAF.", m_outputFile, ArgumentRequired));

     

     // Add optional parameters

                MediaParameters mediaParameters;

                JobSetupUtils::setMediaParameters (mediaParameters,

                                                   m_options.m_masterMobID,

                                                   m_options.m_physicalSourceMobID,

                                                   m_options.m_tapeName,

                                                   m_options.m_psmDescriptorType,

                                                   m_options.m_psmTimecode,

                                                   0);

     

    Additionally - what restrictions are there on the supported formats - specifically is XDCAM / other long GOP formats supported?

  • Wed, Dec 19 2018 1:48 PM In reply to

    • andym
    • Not Ranked
    • Joined on Thu, Jan 13 2011
    • Posts 103
    • Points 1,215
    • Avid Developer Moderator

    Re: AAF Generation using AMT v3

    JamesTV,

    AMT is not intended to create AAFs with a higher complexity than master clips, specifically there is no support for creating composition MOBs (sequences). The purpose of the AAF generated by AMT is to describe media assets comprising multiple Avid Atom media files, typically video, audio and data tracks. Creating such AAFs can be a rather complex operation especially if Long GOP essence and growing files (EWC) are involved so we hope the functionality is not entirely pointless.

    For the described use case (master clips only) all media formats supported by AMT are supported, this includes MPEG-2 and MPEG-4 Long GOP essence.

  • Tue, Jan 8 2019 3:17 PM In reply to

    • JamesTV
    • Not Ranked
    • Joined on Fri, Mar 31 2017
    • Posts 25
    • Points 305

    Re: AAF Generation using AMT v3

    Andy,

    Thanks for the reply - and did not mean to say the implementation was not entirely pointless, it would just be incredibly useful for Avid to offer support within the toolkit for AAF generation for multiple assets.

    However - back to AMT3 and what is there today, I am strugging to generate a MAD XML directly from the tool for a OpAtom asset (e.g. 1 video MXF and multiple audio MXFs). Do we need to generate our our own MAD XML (effectively combining elements of the standalone MAD XMLs for each MXF into a singular one) - ready then for the code to generate an AAF from this XML?

    Do you have an example MAD XML for an OpAtom structure you could share for reference?

Page 1 of 1 (3 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller