Remember "ignore" choice when loading corrupt scores

• Aug 29, 2015 - 04:01
S5 - Suggestion

My MuseScore files are telling me that there is a loading error. Every time I log in to listen and edit the songs I've selected it always go back to it's default setting. This is really annoying and it need to be fixed ASAP.
GIT commit: f51dc11


If your score is corrupt, the way to prevent future complaints is to fix the corruption. If you need help fixing the corruption. see If you still need help, you can ask for it on the Support forum, and attach the score you are having problems with.

It has been suggested that we could add a feature to remember your choice to ignore the corruption and not warn you about it next time. There does not seem to an open issue for this feature request, so I'm re-classifying this issue for that purpose.

@Kevin21 Can you link to a couple of songs that display these errors? Just to make sure we are not missing something.

In any case, I think it's a bad idea to provide a feature to always ignore the corruption. If the score is corrupted, it should be fixed.

These are the following scores that are corrupted at this moment. ( Deoxys Battle Theme Complete, Oracion Pokemon, Pokemon Battle Medley Vol II, Pokemon Champion Battle GSC "Maybe", Pokemon Champion Iris theme B2/W2 "Maybe", Pokemon Champion Steven Theme RSE battle "Maybe", Pokemon Champion Cynthia "Maybe", Pokemon RBY Gym Leader Theme, Vs. the legendary regis "Maybe", Disney Medley.)

I hope you guys make an update soon that involves fixing and removing all disruptive bugs for good. Thanks for the help!!!!

Maybe= possible chance that the score file could be corrupted with a bug of some sort.

All "Pokemon Champions", "Gym Leaders" and the "Legendary Regis" are percussion if you are wanting a little more detail on the scores.

It would help if you actually attached or linked to the scores. But again, it is better to ask for help on the Support forum.

I am guessing these scores were created with older versions of MuseScore. Chances are that the bugs that caused the corruption were fixed long ago, so newly created scores won't have these problems. But you will still have to manually fix the damage that was already done. And even if these are new scores, in order to fix any bugs, we'd need not just a copy of the already-corrupted score, but instructions on how to reproduce the corruption from scratch.

Just one example, "Deoxys Battle Theme Complete". I guess you are talking about

When opened in MuseScore 2.0.2, it said

Measure 31 Staff 3 incomplete. Expected: 4/4; Found: 50/48
Measure 31 Staff 4 incomplete. Expected: 4/4; Found: 50/48
Measure 31 Staff 5 incomplete. Expected: 4/4; Found: 50/48

There is a good reason for that. Take a look to measure 31, staff 3, 4 and 5. It's obvious that these measures are corrupted. The second tuplet should be a quarter note and a 8th note, and not a quarter and dotted 8th note. There is no way we can fix this automatically. It's just wrong in the original file.

Capture d'écran 2015-08-31 08.23.59.png

Seems 'incomplete' is the wrong word there, there's nothing missing, but rather something too much in that measure. It is more a mismatch than incomplete. Maybe we could change those messages to something like "Mismatch in Measure %1 Staff %2. Expected: %3; Found: %4"