Latest post Tue, May 12 2015 12:15 PM by andym. 8 replies.
Page 1 of 1 (9 items)
Sort Posts: Previous Next
  • Wed, Apr 15 2015 2:34 PM

    AMT Generated AAF - Korean Characters not seen (escaped to _)

    We have 2 methods of creating AAF for checkin via Web Services, using our old method we are able to create Korean (3 byte UTF8) characters which display correctly in Interplay/Media Composer. We have, however, recently implemented AMT and using the AMT (2.10.0.923) to create the MXF Atoms and AAF Korean characters are escaped to _

  • Wed, Apr 15 2015 7:49 PM In reply to

    • robg
    • Not Ranked
    • Joined on Fri, Nov 4 2005
    • Tewksbury, MA
    • Posts 494
    • Points 5,605
    • Avid Developer Moderator
      Avid Employee

    Re: AMT Generated AAF - Korean Characters not seen (escaped to _)

    MarquisBroadcast,

    Please send a code snippet and some sample data so we can try to track down the problem here.

    - Rob

     

  • Fri, Apr 17 2015 2:48 PM In reply to

    • robg
    • Not Ranked
    • Joined on Fri, Nov 4 2005
    • Tewksbury, MA
    • Posts 494
    • Points 5,605
    • Avid Developer Moderator
      Avid Employee

    Re: AMT Generated AAF - Korean Characters not seen (escaped to _)

    MarquisBroadcast,

    Update: Our team reproduced this problem in the lab.

    But, if it is readily available, please send your code snippet just to make certain that we are seeing the same issue.

    - Rob

     

  • Mon, Apr 20 2015 2:52 PM In reply to

    Re: AMT Generated AAF - Korean Characters not seen (escaped to _)

    Hi,

    We are using CreateInterplayClip()

    The clip name is being passed as the first parameter (i.e. the local file name) is

    L"c:\\temp\\우리결혼 했어요 예고2 03/06일"

    This has to be converted to "char *" rather than "wchar_t *".

    If we convert it to the "default" code code page, we get a name consisting of mainly '_' for characters that can't be converted. Interplay Access displays the name with the "_" characters.

    If we force the "default" code page to be Korean. The conversion is better, but the AAF generated by the AMT does not contain the correct name. Interplay displays the wrong name.

    If we convert it to UTF-8 the AMT fails with an error code when we try to write the first frame.

    Idealy we would prefer to use UTF-8 or Unicode as this would allow for clip names that are not in the "default" local code page.

    If we use the AAF toolkit to generate the AAF and Atoms, the name is added as Unicode and is displayed correctly in Interplay.

    Thanks.

    Phil Reynnolds

  • Mon, Apr 20 2015 3:30 PM In reply to

    • robg
    • Not Ranked
    • Joined on Fri, Nov 4 2005
    • Tewksbury, MA
    • Posts 494
    • Points 5,605
    • Avid Developer Moderator
      Avid Employee

    Re: AMT Generated AAF - Korean Characters not seen (escaped to _)

    OK, thanks. I sent this info to our developers...

     

  • Mon, May 4 2015 1:39 PM In reply to

    Re: AMT Generated AAF - Korean Characters not seen (escaped to _)

    Any news about this thread ?

    We are also interested with the "non-ascii characters " AMT issue.

    Thanks,

    Gregor.

  • Fri, May 8 2015 3:28 PM In reply to

    • andym
    • Not Ranked
    • Joined on Thu, Jan 13 2011
    • Posts 94
    • Points 1,120
    • Avid Developer Moderator

    Re: AMT Generated AAF - Korean Characters not seen (escaped to _)

    Hi MarquisBroadcast, Gregor,

    Support for internation character sets in the different Avid Workgroup components uses different technologies and APIs so your milage really depends on the specific workflows and combinations of products that are in use.

    • While ISIS, Interplay Production, Interplay MAM and Interplay Central | UX are generally happy with Unicode for the data they handle (but may still have UI limitations regarding things like non-US/European script), some interfaces that rely on exchanging MXF and AAF metadata at the file level may still not be Unicode compliant.
    • In many cases, these interfaces can still handle MBCS (Multibyte Character Set) strings, given that the suitable code pages are used consistently across all participating systems. Proper use of code pages is essential since non-ASCII characters will likely be corrupted if different code pages or locales are used across systems. Functionality at this level is best effort; please refer to the Avid Knowledge Base for some documented limitations.
    • An even smaller set of functions may still only support ASCII reliably on certain platforms, typically because they are designed to handle 'environmental' strings that are not expected to contain international characters. The case reported by MarquisBroadcast is one of those; 'local_amt_specification' is defined as const char* and receives the local AMT file path. The file path is restricted in terms of length and character set and this may lead to the described issue when passing in a MBCS string.
    • In Avid enviroments, file names and paths are considered restricted technical data and typically do not convey information; media files will usually be indexed and accessed via the metadata they contain so file names are normally ASCII character/number combinations. International characters at the file system level are not supported except for very few narrowly defined use cases and languages to simplify multi platform deployments using Windows, Mac and Linux.

    The issue here is that the 'technical' clip name also shows up as display name in Interplay. If you want to set a specific display name, you should be able to do so after or during check-in through Interplay Web Services. (AMT will check in the generated AAF for you but you can turn off this function and handle the check-in yourself, or update the display name after check-in)

    As with any released API, Avid tries to keep the interface stable over major releases. The next major release of AMT is planned to have an updated interface with full Unicode support.

    Andy

     

  • Tue, May 12 2015 8:43 AM In reply to

    Re: AMT Generated AAF - Korean Characters not seen (escaped to _)

    Thanks Andy.

    You are right, the clip display name is not really an issue as you can rename it through IPWS, wich supports UTF-8.

    But the problem still remain with the checkin folder name in EWI mode, wich is specified in the CreateAmtInterplayClip call by the 'interplay_uri' param, a const char* too.

    So Unicode support by AMT would be welcome ...

    Gregor.

  • Tue, May 12 2015 12:15 PM In reply to

    • andym
    • Not Ranked
    • Joined on Thu, Jan 13 2011
    • Posts 94
    • Points 1,120
    • Avid Developer Moderator

    Re: AMT Generated AAF - Korean Characters not seen (escaped to _)

    Gregor, thanks for the explanation. Unicode support for AMT is on the list of features to consider for future releases.

    In the interim, we are working to analyze the exact cause behind the code page limitations.

Page 1 of 1 (9 items)

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