Latest post Fri, Jan 18 2019 10:30 PM by Rich Laws. 1 replies.
I apologize if this is not the correct forum for this post.
We have run into an issue with one of our products in use at a mutual customer in Albania. Our product uses the legacy AMT 2 toolkit with MXF media created with Interplay MAM 5.9.5.10037. (we are in the process of moving to AMT3but still have a period where AMT2 products are in use).
The customer's workflow creates assets (DNxHD and XDCAM-EX 35) using Interplay MAM workflow and the MXF content crashes AMT 2 hard (unhandled exception). The exception occurs in OpenMxfFile call on the video file. NOTE - It seems to be limited to HD formats - IMX50 media created with the same workflow does not have an issue.
Ideally - since AMT2 is essentially no longer in development - a fix to the media creation in Interplay MAM can be identified to maintain compatibility with AMT2 at least with SD and HD formats supported by AMT2. This appears to be a metadata issue.
Please advise and let me know if you need any assistance or have any questions.
More details on this issue... The customer provided us with some XDCAM50 clips (25 fps interlace) created with the same process - Interplay MAM 4.9.5.10037. These work with NO issues with our AMT2 product.
An MXF dump of the XDCAM 50 video file shows metadata that is not present in the other formats mentioned (e.g. coding equations). Based on previous experience with EVS media and AMT2 - AMT2 doesn't default certain video descriptor metadata if it is missing. My theory is that some elements are missing from the descriptor in the DNxHD and XDCAM-EX video files that are causing AMT2 exceptions. In the EVS case - we patched in those missing elements to the MXF header to resolve but don't want to modify Avid media. Obviously, the best case would be a future version of the MAM product to write the needed metadata for AMT2 compatibility if someone can confirm this.