Program crashing because it finds unexpected timing in 2 measures - but I can't fix it.
The program crashed while I was working on an arrangement. New user. In the process of reopening the program and before responding to the "Restore previous file" prompt, I first asked for the details of the problem (as one of the options offered by the dialogue box) and it provided the following:
Measure 7 Staff 1 incomplete. Expected: 3/4; Found: 11/16
Measure 39 Staff 1 incomplete. Expected: 3/4; Found: 11/16
I continued the restore by choosing the "IGNORE" option and the file reopened OK ... with nothing missing that I could see.
BUT ... every time I touch either of the "bad" measures, the program immediately crashes again. My plan was to copy a good measure and paste it to replace both bad measures (which are identical) ... but it will not let me click anywhere on either of the bad measures without crashing ... holding SHIFT or not. I'm stuck with an unusable file and arrangement that I'll have to re-do from scratch. Not a very auspicious introduction to the program ... despite the fact that it is pretty remarkable overall ... if it will actually work.
Is this going to be an ongoing problem? I understand that the program itself inserts the appropriate rests, etc. to maintain the integrity of the timing with each measure ... and I don't know enough as a beginner to know how to override anything to create the problem that apparently is there. I was doing very simple stuff as I learned the program. The most complicated was to create triplets and couplets.
Any help in getting past the ""Don't touch me or I'll crash the program" problem with the errant measures?
Comments
See https://musescore.org/en/node/54721 for more advice on fixing corruptions. If you can't figure something out from that, please attach your score and someone else can try.
Don't touch those corrupt measures then, but a range around them.
I encounter corrupt files a lot, because I mostly use MuseScore to import music from PDF or MIDI files, and there are often problems with both.
As Jojo-Schmitz said, usually the best way is to select a range of bars, starting before and after the corrupt ones, and delete them.
Either save a copy first, so you have that to refer to when you copy them out again (i.e. type them in by hand, with Note Input), or do what I tend to do, which is insert enough blank bars shortly before the bit you need to delete, and copy them in there first. Leave one new blank bar as the first bar you'll delete.
Of course, you might want to verify the deleting the range of bars won't crash it again, first - take a copy and work on that, to be safe.
Also, see if there's an automatic backup file which is better than the corrupt one - those are the ones starting with a dot "." and ending with a comma. There usually is one, and if you're lucky, it might predate the problem. Just rename it, e.g. from
.my-problem.mscz,
to
my-problem-older-copy.mscz
If you can't see any "." files, you need to set your computer to show hidden files. In Windows, it's under Tools->Folder Options, in Windows Explorer (the file browser).
In reply to I encounter corrupt files a by AndyHornBlower
Selecting from the measure before the corruption to the measure after the corruption and exchanging voices 1&2, then deleting voice 2 usually fixes the corruption and IMO is easier then inserting, copying and deleting measures.
In reply to Selecting from the measure by mike320
I've sometimes tried exchanging voices as a quick fix on single bars that don't add up to a full bar, or are longer than one, but I noticed if I swapped them back, I still got the same error when I opened the file, so I'm never sure it's solved the problem properly.
I haven't tried it on a range of bars, spanning one that crashes MuseScore when it's selected though. I'll give that a go next time, to see what happens.