Latest post Tue, Oct 30 2018 3:23 AM by Rich Laws. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • Wed, Oct 24 2018 2:48 PM

    • Rich Laws
    • Not Ranked
    • Joined on Wed, Oct 17 2012
    • Posts 65
    • Points 615

    Question about Ancillary Data files created by InterplayMAM.MPI process

    Hello,

    We are working on an issue with a mutual client in Turkey.  Their Interplay system has a number of clips with an associated data MXF file.  (resolution shows as "Data", track as D1).  Admittedly we have not much experience with these "data" MXF files.   My initial question before more research into our MXF scan is to ask if these MXF files are expected to conform to the typical KLV pattern of all MXF files?

    We have a process that does an MXF "sanity check" on all MXF files and the data files don't seem to be constructed correctly. (at least as our analyzer checks).  There is a block following a filler block that has no SMPTE label and causes the scanner to fail. (as viewed by hex dump)

    The ID section shows the data file (and media files) are created with InterplayMAM.MPI version 4.3.11.1217.  The media files associated with this clip are all scanned correctly.   Is there an addendum or MXF change that we should be referencing or are these to be treated as "custom Avid" and ignored by our tools?

    Just a question looking for more info or advice...  :)

    Thanks,

    Rich

  • Tue, Oct 30 2018 3:23 AM In reply to

    • Rich Laws
    • Not Ranked
    • Joined on Wed, Oct 17 2012
    • Posts 65
    • Points 615

    Re: Question about Ancillary Data files created by InterplayMAM.MPI process

    Replying to my own message...  We are closing this issue for now.

    Update:

    This client (Teratek) has told us that these ancillary MXF files apparently caused them an issue with Avid tools some time ago and were told by Avid support to delete them from Avid shared storage.  (This occurred after our system archived the files)  In any event - these invalid ancillary files were created with InterplayMAM.MPI  4.3.11.1217.  

    We checked a dozen or so ancillary mxf files at ANOTHER client site (created with an older version InterplayMAM.MPI  4.3.5.947) and ALL of these are valid MXF files with expected MXF structure.  The files are valid in both the archive and online versions.

    Our current archive s/w will prevent invalid mxf files from being archived or restored - so the client will receive a notice of any invalid files and handle on a case by case basis.    We are unsure why the client has the ancillary files with an invalid data block but it should not be an issue with our workflow.

     

Page 1 of 1 (2 items)

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