MuseScore Thinks My .xml File Is Corrupted

• Aug 12, 2024 - 02:38

Something very odd is happening to my file. After creating the .mscz file, then saving it as a .xml file to open with Lime Aloud (a program that uses Braille and speech so musicians who are blind can create music), when I save that file as a .xml from a .lim (the default file extension for Lime Aloud), MuseScore says that the file is corrupted for some strange reason. When a music file is saved as a .xml, it should work just fine, regardless of which music app you use. Is there a way to fix this issue?
Attached is the .xml file that I worked on.

Attachment Size
Olympic Reel.xml 2.2 MB

Comments

MuseScore reports that bar 444 in staff 1 is corrupted but still opens the file.
Checking bar 444 in staff 1, I notice there is something odd notated for the 3th and 4th beat.
Maybe other programs are just ignoring this.
Not sure why this corruption occurs. Perhaps you can also attached the original MuseScore file to check?

In the MusicXML file generated by Lime Aloud, the third triplet in measure 444 (A C C E) starts with a nested triplet, which MuseScore's MusicXML importer cannot yet handle.

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