Musescore crashed and did not auto-save, deleting hours of work

• Dec 23, 2022 - 03:26
Reported version
4.x-dev
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Once
Status
needs info
Regression
No
Workaround
No
Project
MuseScore
  1. I used the arrow keys to adjust a note.
  2. My cursor showed a loading symbol.
  3. The program closed completely.
  4. Upon reopening, there was no message prompting restoration of work and the file is showing a "last modified" date of over a month ago.

Comments

• Dec 23, 2022 - 08:37
Title Musescore 4 crashed and did not auto-save, deleting hours of work ⇒ Musescore crashed and did not auto-save, deleting hours of work
Reproducibility Always ⇒ Once
Reported version 3.6 ⇒ 4.x-dev

Is there any way you can reproduce this issue? It seems like this only happened the one time.

Reply

• Dec 23, 2022 - 09:10
Status active ⇒ needs info

Was this score created in an earlier version of musescore, and if so, have you saved it since converting it?

Reply

• Dec 23, 2022 - 15:44

If you had performed hours of work and the last modified date on the file you are looking at is still showing a modified date from a month ago, then either a) you never saved the file (in which case, that is unfortunate but you are expected to save your work!), or b) the file you were working on for hours and saving regularly isn't the file you are looking at. could be you were actually opening another copy of the file from another folder.

Either way, there is also an autosave file MueScore creates automatically for disaster recovery like this. If you say what version of MuseScore and what OS, we can help you find it.

Reply