File Corrupted
Now that Sept 1st has been established as the cutoff for editing an uploaded Version 1.3 score, I'm trying to develop duplicate scores in Version 2.1. On one score I'm getting the error message of "File Corrupted". The detail of the "corruption" is:
"Measures 178 (& 179) Staff 1 incomplete. Expected: 6/8; Found: 38/48"
Version 1.3 had no problem with these measures and they are exactly as Chopin wrote them. I am attaching the file. Can anyone suggest how to "fix" these measures for Version 2.1?
Thank you.
| Attachment | Size |
|---|---|
| Chopin Ballade No. 4 V2.1.mscz | 117.91 KB |
Comments
These tuplets are wrong. Some of them contains a eighth note rest and a eighth note.
Find attached a fixed file.
In reply to These tuplets are wrong. Some by [DELETED] 5
I get it. In 3 places I should have used a sextuplet for the first voice 8th notes. Thanks.
Was this score imported from 1.3 and then edited in 2.0.1 (note: not 2.1, that's still a long ways off), or was it created from scratch in 2.0.1?
1.3 definitely had quite a lot of bugs where it would create corrupt measures, and it lacked any sort of sanity check to detect the corruptions it created. For 2.0, we fixed all the causes of corruption in 1.3 we could identify, so it won't cause corruption in those same cases, plus there is now a sanity check on load, so it reports the corruptions that 1.3 caused but never detected.
Loading the original 1.3 version of your score (which I found on musescore.com), I see the same error, so it appears this is one of those cases of corruption caused by a bug in 1.3 that MuseScore never used to notice but now does. Many of the known causes of corruption that were fixed had to do with tuplets - particularly in conjunction with copy and paste, multiple voices, and/or nesting tuplets. So hopefully whatever caused this problem in 1.3 is already fixed in 2.0, so new scores you create won't become corrupt in this same manner.
That said, it's unlikely we found every possible cause of corruption in 1.3, so some probably still remain. And it's also unlikely we managed to avoid creating any new cases. If you see corruption happening in a score created from scratch in 2.0, do let us know, and share any insight if you can into what you think might have triggered it.