Crash After Crash Recovery

• Sep 9, 2020 - 03:42
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
MuseScore

I am beyond livid, but I will try to keep my closure.

I was working on my fifth quartet as I reached a point where I needed to change time signatures every other measure frequently. In a particular part, it crashed as I put 3/4 in place after a 4/4 measure. I reopened musescore and as usual, it gave me the option to "restart the previous session." I did, and I went on placing the 3/4 measure where I intended it to be (some other notes were lost and easy fixes), and it crashed again. I reopened it, gave me the same option to "restart the previous session," but it wasn't the previous session. It was an earlier saved version of my piece and the file opened that way too.

The reason it feels excruciating to me is because the entire trio section was simply lost. Naturally, I want to punch anyone who could be responsible, but alas it wouldn't do any good even if the perpetrator was human. It was the first time I managed to write in a waltz form and it's just gone.

All I want is closure, since I'm sure near to nothing can be done. It may not do any good, but I attached the version of the piece that was saved so long ago before I began to write the waltz section. I'm not a "techy" type person, so please help me.

Attachment Size
String Quartet No.5 in B flat Major; II.mscz 40.88 KB

Comments

• Sep 9, 2020 - 03:49
Regression Yes ⇒ No
Severity S3 - Major ⇒ S2 - Critical
Type Performance ⇒ Functional

I'm curious if the crash happened when you put the time signature into the last measure of the score. If so, I expect it would be an easy bug to reproduce and ultimately fix.

Currently there is no way to add another time signature without adding another measure. If you could explain step-by-step what to do with this score to cause your crash it would help.

Reply

• Sep 9, 2020 - 07:55

and it crashed again. I reopened it, gave me the same option to "restart the previous session," but it wasn't the previous session. It was an earlier saved version of my piece and the file opened that way too.
That probably is because the autosave timer hadn't yet fired (every 2 minutes by default), so there was no new auotsave file being created and so picked on the last one instead

Reply

• Sep 9, 2020 - 19:12

To begin with, my score was completely different from the one seen -- it was broken apart and sections where deleted and added and ya know other random music things people do when composing.

There were a series of 3/4 measures and I had written with empty individual measures in between each one measure phrase with fermatas.

I then deleted these fermata measures, except I had added a quarter note lengthed (4 semisemiquavers) upbeat in one of these measures.

My plan was to make the phrased measure before the measure with the upbeat in 4/4, that way the upbeat fit. I began to do this by putting another 3/4 where the 3/4 time would return one measure later, and then I'd try and implement the 4/4 measure where I wanted it to be. That was when it crashed and the drama began. It crashed, then musescore reloaded it for me again when I opened it; I tried the same thing I was trying to do (musescore has crashed on me numerous times but I've always gotten through smoothly doing what I was trying to do), but it didn't open up the version I was working on.

If there is possibly more to it, I did add heavy tempo changes in sections before the cause of the crash.

Reply