Bug: Score corrupted pop-up error
My score became corrupted this morning, again, sigh. This is a score different from the previous one that became corrupted, but I am seeing a common event causing the corruption (dotted notes).
Here is a screenshot (https://imgur.com/a/SptXsB0) of the score that suddenly became corrupted. It is a simple cluster exercise score, 3/4 time. All I was doing (and this same situation caused the prior corruption on a different score) was changing quarter notes in the final measure (bass clef) into dotted half notes, when boom that caused the error to pop up for the score being corrupted. So I think it is something to do with the "dotted note" shortcut glyph in some way. As can be seen in the screenshot, that final bass clef measure shows the dotted half notes followed by an eight note rest which does not belong there as the dotted half notes complete a 3/4 time measure.
The score was originally 4/4 time, maybe 6 measures. Then I converted it to 3/4 time. The score corruption pop-up error notice happened when I was created dotted half notes for a block chord, when that last measure showed the dotted half notes chord and an eighth note rest that made the measure appear to be 4/4 time when in fact it should have been 3/4 time.
(For anybody curious, the composing exercise I was doing was Exercise 37:Clusters from "Composing with Constraints 100 Practical Exercises in Music Composition" by Jorge Variego.)
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.2-242570931, revision: 3130f97
| Attachment | Size |
|---|---|
| Corrupted-Exercise 37 Clusters.png | 88.08 KB |
Comments
> when that last measure showed the dotted half notes chord and an eighth note rest that made the measure appear to be 4/4 time when in fact it should have been 3/4 time.
No, this measure is not a 4/4 but a 7/8 measure.
If this is the only mistake in your score: delete the eighth rest with Ctrl+Del!
If it is not: attach the score.
In reply to > when that last measure… by HildeK
I could not delete the eighth rest-- as soon as it automatically appeared after I created the dotted half notes the crash occurred along with the pop-up error notifying me about the crash. I did attach a screenshot of the score. I have attached that screenshot again here, along with my 'finished' score; when Musescore crashed, I had the option to revert to the last saved version I chose that rather than lose my work-- then I finished off the score and that is attached as a Musescore file.
In reply to I could not delete the… by randall_oelerich
We really needed a version of the score that was corrupt. Did you look at the Show Details?
In reply to We really needed a version… by bobjp
No. I was more interested in preserving a copy of most recent save that was not corrupt, so as to no lose my work. The next time it happens I will see if there is a Show Details button and take a look.
This has happened to me twice now, on two different scores, in the past couple of weeks. I am going to see if there is a version of Musescore that a month old etc that maybe I can install and get a version that does not keep crashing / corrupting my scores.
In reply to No. I was more interested in… by randall_oelerich
I've never had any version corrupt a score. That's why it would be nice to see what is going on a
in a score that has this happen to you. Of course, I don't want it to happen to you.....but if it does, please post the score. The Details button will present a list of problems that you can save for later use, for fix right then. Then you can choose to revert to a different version, or close.
In reply to No. I was more interested in… by randall_oelerich
Please consider score versioning to mitigate losses due to corrupted scores.
See https://musescore.org/en/node/369244
Please attach diagnostic file: Menu -> Diagnostic -> Save diagnostic file
In reply to Please attach diagnostic… by mercuree
I could not attach the diagnostic file, it exceeded the maximum attachment file size.
In reply to I could not attach the… by randall_oelerich
I need log files only.
Please go to AppData\Local\MuseScore\MuseScore4\logs folder (WIN + R, type %USERPROFILE%\AppData\Local\MuseScore\Musescore4\Logs and press ENTER)
Make a zip archive of those files with .log extension and try to attach it here. Don't include dumps folder.
In reply to I need log files only… by mercuree
I am going to have to wait for this issue to happen again. At this point in time, I am really uncertain which log files to share, because at this point I honestly can not recall which computer and operating system the bug happened on. I have a desktop PC with Musescore on both Windows 10 and Linun, and the same for my laptop. I think it was Windows 10 on my desktop but I can not be sure.