Hi Marianna, Do you have any updates on these cases? Thanks, Luis

Hi Marianna, Thank you for helping us with these cases. We have contacted Dennis as well regarding this case and will continue to do so in the future. I will wait for any information you have for me. Thanks, Luis

Hello, I am a Capella support engineer looking for some help with two customers facing some issues with the Capella and AVID integration. I have added links to packages with sources, outputs, and projects to help reproduce the issues. Blank File Name: (https://www.dropbox.com/s/ycgfhbezproyjlo/13906.zip?dl=0): One of our customers is having a problem

Hello, When we create such a file (MXF XDCAM HD422 interlaced), MediaInfo reports the scan type as progressive, but scan order is shown to be Top Field First. We received a complaint and can't say for sure that the file created should work fine. We are using 4.4.28.10055 (with AvidMXF_SDK_4.6.44_vc12.dll and MediaProcessor_4.4.28_vc12.dll). The

This was coming from a customer but we didn't get any more information. Seems like it needed to match some internal naming scheme. We are considering this closed as this is no longer needed for them.

Is there any way from the SDK to control the names of the individual MXF files created? By default naming is something like AudioFileA0180E5FA48.mxf, AudioFileA0280E5FA49.mxf, etc

Thank you! I updated to a newer AMT version and it now works fine.

Thank you, I tried to implement this but couldn't get it to work. According to this, the feature is targeted to be available in AMT 3.12: http://cstest.avid.com/forums/p/196904/881838.aspx ...but currently I am using AMT-3.11.0. Is this info still correct? Any release schedule info for 3.12?

We got a request to add some metadata to the .AAF file. In the output sample we received, analyzing the file using MXFDump shows that the metadata is stored in the .AAF file as a 'AAFTaggedValue'. Is this something that be added using the AMT3 SDK as we create the AAF file? If not, is there a suggestion for how this could be done?

We've noticed errors when using AMT if the MOB IDs don't follow the proper format. For example, if we set it to 'test' instead of something like '060a2b340101010101010f0013-000000-4fd6340fea6337e1-060e2b347f7e-2a81'. We'd like to do some validation of these values before passing them to the AMT SDK. Is there a description