MusicXML - Example Set

• Dec 30, 2012 - 06:10

I recently came across this .

One at a time, I tried to open the .xml files that were in the .zip: 'BrookeWestSample' caused a crash, whilst both 'MozaChloSample' and 'MozaVeilSample' claimed not to be valid MusicXML files, but still appeared.

Leon, I wondered if you were able to look through the scores to see if they import correctly? I've noticed a few things and could take notes, but thought it might be better if I just left it to you for the moment? After fixes are made, we could look at it again. What do you think?

There's also some things that pertain to MuseScore itself, so it might also be good if Werner was able to look at some point.

Using MuseScore 2.0 Nightly Build (3df14c5) - Mac 10.7.5.

Comments

• Dec 30, 2012 - 10:53

Thanks for pointing this out.

My typical way of working is to run all MakeMusic (formerly Recordare) samples through MuseScore shortly before the public test cycle of a new release starts and fix all critical issues. Same goes for Reinhold Kainhofers Unofficial MusicXML test suite at http://kainhofer.com/musicxml/.

Any help in ensuring optimum MusicXML compatibility is welcome. Feel free to test and report any issues you find. More testers typically means better test coverage.

Reply

• Dec 31, 2012 - 02:33

About that test suite, I tried '01b-Pitches-Intervals.xml’ in a number of applications and it didn't reflect the result on the website (which uses LilyPond) - it appeared without bar lines and either no time signature, or a common time signature.

Reply

Do you still have an unanswered question? Please log in first to post your question.