Corrupted file won't open

• Jun 28, 2023 - 01:37

I was working on a score (it's a very simple, silly project) and trying to adjust the voltas to make it clear when the final repeat starts (for some reason adding a coda wasn't working for me) and the project kept crashing. Not sure where to find the autosave. Every time I try opening the file, MuseScore crashes. Please help me find/correct the corrupted measure so I can finish this? Thank you!

Attachment Size
moose - better.mscz 132.44 KB

Comments

I don't know why MuS 4 crashes.
Using v. 3.6.2 it opens the mscx (o.k., I'd some problems with the measure repeat sign in the drums) and I noticed that the repeat list of the volta is specified wrong.
For the first volta you should specify "1,2" and for the second "3". And the measure properties of m. 17 should have '3' for the 'Play count'.

See my corrections done in MuS 3.6.2. Maybe you need to reformat the title block.

Attachment Size
moose - better_3.6.2.mscz 33.69 KB

FWIW, your score opens with no errors in 4.1, due to be released next week. So it looks like whatever bug caused the crash, is fixed. No corruption is reported either. You can grab the beta from the Announcements forum.

For future reference, the autosave probably would be useful here - it's going to be almost identical to the actual score except it might contain the last few minutes of editing. But you can access it by enabling hidden files/folders in your OS, then looking for files ending in ".autosave" int he same folder as your score. Probably more likely to be useful would be the backup, also hidden, look for the ".mscbackup" folder.

Also, if you're having adding the DS(DC) al Coda / To Coda / Coda combination (be sure to add all three elements - it won't work with only one or two), feel free to start a new thread asking for help on that, explaining what you are doing and what goes wrong when you do.

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