Musescore 2 Corrupting Files

• May 26, 2015 - 16:51

Whenever I save and reopen a file it tells me that score is corrupted as per below. However, the measures are all correct and the score plays and functions perfectly before I save it. As soon as I save and reopen the file it is corrupted. I have tried several times on 2 different computers and am having the same issue. The score was created from scratch and no measure duration were manually changed. However upon reopening ALL measures have the same error (see sample below). Anyone know how to fix this issue?

It really irritates me when companies publish updates that have so many bugs - especially when the old program was working great.

Sample Error Message:
Measure 1 Staff 1 incomplete. Expected: 4/4; Found: 8/16
Measure 2 Staff 1 incomplete. Expected: 4/4; Found: 8/16


Pretty hard to tell without seeing the score.
Also need to know ewich version or MuseScore, what OS and how that file got got created (MIDI import? XML-Import??
MuseScore 2.0 does detect ccorruptions, 1.x did not, so don't shoot the messenger ;-)

Yikes! Sounds like some serious problems. Please attach the score here so we can take a look at it and figure out what on Earth is going on.

FWIW, the list of bugs fixed between from 1.3 to 2.0 is enormous. Just because you weren't running into them doesn't mean they weren't there. There are bugs in any software release, but actually, the list of known bugs in 2.0.1 is not unusually long. And keep in mind, MuseScore isn't produced by a "company" in the usual sense - it is open source software, produced and tested by volunteers who are just fellow users of the software like yourself. There was an eight-month long public beta period during which hundreds of your fellow users were helping test. I'm sorry the particular bug you seem to be hitting was not found by any of those people during any of that time, but it's not like this was just rushed out. If you would like to see fewer bugs next release, your participation in the testing process would be most welcome!

Anyhow, since you say this happens on two different computers and the score is created from scratch, I assume that means you can provide step by step instructions to reproduce the problem? Simply posting the already corrupted score won't help much - we'll need to to know how it got that way.

I have the same problem. I created a score in 2.0.0, saved and closed. Then I downloaded 2.0.1 and tried to open the same score, and it says the file is corrupt and it won't let me view. Attached is the .mscz file and screenshot of the error message. Thanks.

EDIT: Though when I press "Ignore" in the error box, everything *seems* to work fine.

In reply to by cloudSlayer

If you press "Details", it tells you exactly where the problem is: measure 4. And if you count the beats, and use the status bar to help you see which notes are on which beats, you'll see there is indeed a problem in that measure. I think you are probably seeing this bug: #61476: Corruption reading empty measure with 7/4 actual duration, which ahs already been fixed and should be in the next update. It's a problem that only affects long long measures with whole rests in them. For now, the workaround seems to be to avoid using whole rests in long measures. See if the attached works better for you.

Attachment Size
Chant_Alleluia fixed.mscz 168.98 KB

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