Would this be due to malformed xml?
Can you attach the MusicXML file thatâs producing this validation error? It would certainly appear that thereâs something not quite right in the MusicXML file youâre importing. If you can attach it here, we can get in touch with the developer of the application thatâs responsible and alert them to the problem.
Hmm. I can attach the file of the next import that throws an error. It seems to happen on repeats, both standard and 1,2 endings, but not consistently (and often gives no error but the repeats just donât repeat). Easy enough to fix and not really a big deal. I was curious as to why, like âIs this just internet music xml that lost something in the conversion? Or is it an internal import thing?â I thought I may have had to fiddle with the import settings in Dorico ipad to make them work."
Ach, I should have read the error msg I posted 1st. It is beautifully informative. Attached is the .mxml file that threw the above import error.
BWV_0991.zip (5.2 KB)
Thanks for the reply, Daniel
Stupid emojis. The idiotic smily face should have been my clever ascii repeat line, lol. â: |â
When I tried importing this into Dorico Pro 5, I got the same error message.
Because the various music notation applications (Dorico, Finale, Sibleius, MuseScore) do have differences in their handling of musicxml import and export, I tried importing it into MuseScore 4 for a comparison. I received a similar error message but truncated to just a few lines.
Here are 4 files for you to âplay withâ and compare, etc.:
-
The original file (BWV_0991) after being imported into MuseScore 4 and then exported as a .mxl file.
BWV_0991 (via MuSc).mxl.zip (7.6 KB) -
The original file (BWV_0991) after being imported into MuseScore 4 and then exported as a PDF.
BWV_0991 (from MuSc).pdf (62.4 KB) -
The original file (BWV_0991) after being imported into Dorico Pro 5 and then exported as a .musicxml file.
BWV_0991 - Full score - 01 BWV_0991.musicxml.zip (5.3 KB) -
The original file (BWV_0991) after being imported into Dorico Pro 5 and then printed to a PDF.
01 - Full score - BWV_0991.pdf (60.0 KB)
For each import I had to click on âignore errorsâ, after which the file opened. I was then able to export/save/ print.
So it would appear the xml is the culprit. Like you say, the importing/exporting/converting of scores between various programs is bound to introduce incompatabilities. .mxl sure has come a long way, though. Sure beats editting midi with a text editor like back in the day. Thanks for verifying the problem. I feel more confident knowing that it wasnât anything I neglected on my end. I too just ignored the errors on BWV991 above and it imports fine with the exception of barline repeats and repeat endings. All the notes and articulations (that werenât text) translated well.
Clarification: Articulations and notes from other scores (that have articulations) , which threw the same type of errors (repeats being unresolved) during import work mostly fine. The repeats come into the Dorico import ok, they just donât loop. Iâll just replace them during the cleanup phase (text articulations to system articulations, inserting movements into flows, fixing sour notes and timing, instrumentation, balancing the mix, etc etc).
The problem is indeed with the MusicXML file. It looks like the producing application, CapToXML, is incorrectly appending a full stop (period) to the text that appears in the repeat ending. This is invalid according to the MusicXML schema: the number
attribute can contain a comma separated list of numbers, either with or without spaces in between them, but it canât contain a full stop (period).
Are you using the latest version of CapToXML? If not, it might be worth looking into an update: itâs only exporting MusicXML 2.0, which is a pretty old version of the format by now. If you are running the latest version, Iâll get in touch with the people at Capella to let them know about this problem.
I am not the person who did the actual conversions, just downloaded them as-is from the internet. The site I get these .mxl scores from has the original capella files as well for the scores I am interested in, so it may make sense to re-export the .cap files to .mxl with a newer version of capella. That, or just fix what needs fixing (which is something I do anyway).
Really these problems need to be reported to the developer of the software producing the MusicXML files, rather than to us.
Ok, Got it.