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 media file name (while some other characters get translated to underscores - eg illegal file path chars like colon or question mark become underscore).

Clip name: Shard of Glass’ 3.jpg

media file name: shard of glass’ 3.5d1c5c60v.mxf

Other chars from the extended ASCII set work with no issue.  Perhaps because this is a delimiter it causes an error.  NOTE - customer tried to ZIP these files to send to us and the ZIP utility failed on these files because of the name.

I have a few questions that I'm hoping fror advice with:

1 - Should the editor be filtering out additional characters that may or may not with AMT2? (eg. replacing with underscores?)  NOTE because zip fails these are not very portable file names.

2 - Is there a workaround without renaming the media file before submitting to AMT2 (use case is adding a resolution to an existing clip so this would mean renaming a live media file potentially.  Copy is not a great option some of these are large files).

3 - Is there a list of chars that will and will not work with AMT2?  I can brute force test the set but maybe a list exists.

Any comments or advice is always appreciated!

Thanks!

Rich Laws

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, 

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 name per file system rules so that is omitted.

We will screen clips with media file names that contain these chars for now mark them as incompatible media file names for the toolkit for now.

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 cannot be opened by a legacy product using AMT2.  NOTE - I can open these files with standard c++ fopen_s with no error.  The issue is not with ALL extended characters - just some...

I'm in the position of trying to explain why the tool works with some clips and not others.  (NOTE just replacing the filename - character in Avid storage - and re-indexing - lets AMT2 do it's thing).  I'm looking for a list so that I can screen correctly.

Thanks

Rich