Hi Stuart, It was never responded to. Thanks, Rich Laws

In case anyone else encounters this, I wrote a test program to try all chars (dec 128 to 255) with AMT2 OpenMxfFile File names with these work: ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþ

Hi all, I was wondering if one of the AMT2 developer's can provide a list of which ANSI chars will cause OpenMxfFile to fail with error code 7 (AMT_COULD_NOT_INITIALIZE_MEDIA_READER)? We have a client in Albania who continues to add some extended ASCII chars to clip names on the editor (18.4) resulting in media file names with these chars - that

Some quick testing seems to indicate the issue is with the 4 characters hex value 0x91, 0x92, 0x93 and 0x94. Left and right single quotation mark, Left and right double quotation mark These can be used with clip names in MC 18.4 and end up in the media file names. NOTE - single quote hex 0x27 - is no issue. double quote (0x22) can't be in a file

Hi all, I'm hoping for some advice on handling media file names with certain chars that fail with AMT2 OpenMxfFile (error code 7 - AMT_COULD_NOT_INITIALIZE_MEDIA_READER) A mutual client in Albania creates some clips with Media Composer 18.4 that have ascii char value 0x92 (single right apos) in the clip name. This character passes through to the

Update to this issue. Resolved with editor update from 18.9 to 18.11. We loaded Media Composer 18.11 at our facility - making the same length mix down clip with this newer editor version resovles the issue. THe duration in the audio descriptor is no longer less than the expected length. Tested several known mixdown lengths that caused the issue with

Hi all, Just a note as I have been working with a customer in Argentina with a partial offline issue. In this workflow, the customer is using our product to add proxy audio to existing audio only clips created by Media Composer 18.9. The PAM status shows that the proxy audio is "partial offline" randomly for some clips. What I have found is

Hi Dennis Thank you for the follow up. It is an issue that we can workaround by including the needed MS library in our installer package. My inquiry was more informational for the team. Should I still log through support portal? Rich

Hi Andy, Thanks for the response. I was guessing that it was an external library. We can workaround this in the meantime. Rich

As a note, in the newly release distribution: mediaprocessor-win-vc14-x64-4.4.28.10055, FTF.DLL still has a VC++ 2013 runtime dependency in the 2015 version. (requires installers to include VC 2013 support). Let me know if this cannot be changed and I wil make sure that our installers provide VC2015 and VC2013 lib support. Thanks! Rich