XML files being corrupted

• May 9, 2018 - 02:21

Every time I export my song as an .xml file, and I try to open the file (to see if it worked,) the file is corrupted. Am I doing something wrong? I haven't had this problem before, even on this song--I've successfully made .xml files, but I no longer can do so. Thanks!


Comments

In reply to by gmanhoffman

The uploaded .xml file will not be secure.

You may be able to share the file to someone trusted in this forum from a cloud location in Dropbox , Google Drive or whatever. Trusted and willing to look at the file.

Can you create an export of an unrelated file and see if it is also corrupted? If so, post that.

Or you may be able to narrow down the issue. Make a copy of the .mscz for test purposes. Delete the final half of the score. Now export it. If that is good, there likely is some problem in the section that was deleted.

So, make another copy and delete the first half of the score to confirm.

You can keep working with smaller sections this way until you are down to one small section, maybe a measure of two.

So tried opening one, and when it didn't work, I hit the "show details" button to try and get an explanation. This is what I got. (I shortened it for space; it did this for all 72 measures.)

Measure 1 Staff 3 incomplete. Expected: 1/8; Found: 0/1
Measure 1 Staff 4 incomplete. Expected: 1/8; Found: 0/1
Measure 1 Staff 5 incomplete. Expected: 1/8; Found: 0/1
Measure 2 Staff 3 incomplete. Expected: 4/4; Found: 0/1
Measure 2 Staff 4 incomplete. Expected: 4/4; Found: 0/1
Measure 2 Staff 5 incomplete. Expected: 4/4; Found: 0/1
Measure 3 Staff 3 incomplete. Expected: 4/4; Found: 0/1
Measure 3 Staff 4 incomplete. Expected: 4/4; Found: 0/1
Measure 3 Staff 5 incomplete. Expected: 4/4; Found: 0/1
Measure 4 Staff 3 incomplete. Expected: 4/4; Found: 0/1
Measure 4 Staff 4 incomplete. Expected: 4/4; Found: 0/1
Measure 4 Staff 5 incomplete. Expected: 4/4; Found: 0/1

Also, interestingly, all of my already-existing xml files are corrupt, whereas a song that I'm only 8 or so measures into doesn't get corrupted when I make an xml. And all of these "corrupt" xml files are ones that I know used to work.

In reply to by gmanhoffman

I have a suspicion that the culprit is version 2.2.1 exporting the files differently than version 2.1. I was looking for a portable version of version 2.1 but I'm only finding complete installs. Downloading an earlier version would likely overwrite your version 2.2.1. It might be worth if for you to try. Older versions can be found here.

Another option is to upload it as private to MuseScore.com then download the musicxml file. This is the same format as xml, the suffix has changed in MusicXML version 3.0 which is what MuseScore changed to starting in version 2.2.

In reply to by mike320

I tried the second option, but it still produced a corrupted file. And I don't know that I'd even be able to open the normal file in an older version because I've edited it using the newer one. Also, whenever I try to first open an XML file, I get a window say its not a valid xml file. When I hit "show details", I got this:

Fatal error: line 4690 column 10 Unexpected ' '.

I don't really know what that means. Could you shed some light on that?

In reply to by gmanhoffman

" Could you shed some light on that?"
To assist you, there is not other way for someone can be check by attaching your file. It's simple. If you prefer, attach an excerpt of this file demonstrating the problem by selecting some or more measures, and go in menu "File" -> Save selection

In reply to by Jojo-Schmitz

So for windows it would be MuseScore-2.1-win32_noSSE2.7z 2

The reason I was looking for a portable version is because you can have both 2.2.1 ans a portable version of 2.1 on your system at the same time. There should be very few differences between opening a file in version 2.1 or 2.2.1 and one version should never report an error when the other does not. There is one known instance where an error/corruption is reported and that is when a measure ends in some tuplets. The measure made in 2.1 or earlier will become corrupted in 2.2.1 while it was not in earlier versions.

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