Potential problem with special characters in Cubase/Nuendo files

Non-English versions of Cubase/Nuendo might save localized characters in its files; localized characters that are stored in a way that is not compliant with xml standards. English versions can also be affected if any component (e.g. a macro name) include special characters.

Due to the erroneous xml file format, version 1.4 of the Cubase plugin and version 1.0 of the Nuendo plugin are unable to read these files and the intended Cubase/Nuendo integration will fail.  

The problem is fixed in version 1.4.6/1.0.3

===================================================================================

The following characters are handled by the published plugin (Cubase 1.4.6, Nuendo 1.0.3):

¢¥^¨«±´·½ÀÃÆÉÌÏÒÕØÛÞáäçêíðóöùüÿ¡£¦¬¯²µ¸»¾ÁÄÇÊÍÐÓÖÙÜßâåèëîñô÷úý¤§ª°³¶¹¼¿ÂÅÈËÎÑÔ×ÚÝàãæéìïòõøûþ`½¤$€

===================================================================================

What to do if you get this problem?

The thing that happens is that you get an error saying that "Key Commands.xml" could not be read.  

• Check your macros and Logical Editor Presets if their names have some special characters that are not in the list above.
  
• You could try to open the file in a web browser, it will have the same problems as the plugin to read the file. If the problem is due to special characters the web browser will  stop at the character and give an error message.
  
• You could have a look in the pluginlog.log file. It's a very technical log but you might spot an exception message saying something about characters.
  

If you find that the problem is caused by some character that is not in the list of handled characters above I would appreciate if you reported this with the pluginlog.log and Key Commands.xml files zipped as an attachment. Unfortunately the only way to get passed the problem with the current plugin release is to get rid of the problem characters from the Cubase/Nuendo file.