Skip to main content
Recent Posts
71
User Tools / Re: NWCCONVERTOR
Last post by Lawrie Pardy -
Hi Gust,
confirmed.  Perhaps, given this is a problem that will certainly occur in the future, you could specifically check for these problems during conversion and either delete or replace them with a flag - maybe "BLANK"?

Also, and I don't know if it's a problem specific to my installation or Win11, NWCCONVERTOR can't seem to remember how to open the MusicXML file with Musescore.  The correct path is in the options screen, but if you press OK, the config file is updated without the entry, UNLESS your browse to it beforehand.  Then if you press OK the config file is saved with the correct path and it all works until next time you run NWCCONVERTOR, where, even though the correct path is in the config file, NWCCONVERTOR ignores it and you have to browse to it again...
72
User Tools / Re: NWCCONVERTOR
Last post by Flurmy -
pencil-button.png is missing in the .zip.
There's no way to include it permanently in the .exe?
73
User Tools / Re: NWCCONVERTOR
Last post by Flurmy -
More generally, the following chars must be "escaped" in xml:
Quote
"   "
'   '
<   &lt;
>   &gt;
&   &amp;
74
User Tools / Re: NWCCONVERTOR
Last post by Flurmy -
Quote
The ampersand character (&) and the left angle bracket (<) MUST NOT appear in their literal form, except when used as markup delimiters, or within a comment, a processing instruction, or a CDATA section. If they are needed elsewhere, they MUST be escaped using either numeric character references or the strings "&amp;" and "&lt;" respectively.
The right angle bracket (>) may be represented using the string "&gt;", and MUST, for compatibility, be escaped using either "&gt;" or a character reference when it appears in the string "]]>" in content, when that string is not marking the end of a CDATA section.
75
User Tools / Re: NWCCONVERTOR
Last post by Opagust -
Hi Lawrie,

The problem is in the author and copyright fields in  the File info of your nwctxt file, which contain "<Name>" and "<Year>".
The '<' and '>' characters are interpreted as tag delimiters in a musicxml file. Their presence in text fields makes the file invalid.



76
User Tools / Re: NWCCONVERTOR
Last post by Lawrie Pardy -
Hey Gust,
thanks for the quick response.  I tried this quick test file and Musescore didn't like it at all, it threw 39 errors, though NWCConvertor seemed happy.

The source .nwctxt file is just the first one that I found on my system when I went looking for a test file.
The MusicXML file is the output from V 2.0.05.05 (NB I had to ad .txt to the filename to get it to upload - you will need to remove this for Musescore to recognise it)

I concede this may be an unfair test...
80
User Tools / Re: NWCCONVERTOR
Last post by Opagust -
I'd like to have an working example.

I managed to create it myself, but when I exported it to MusicXml and re-imported that file into Musescore, the flow was ignoring the coda's again.

So: if Musescore can't create a correct a correct coda-working musicxml file, why should I bother?