Incomplete bar causes musescore to crash
I have a bar at the end of my score that only shows a crotchet and the rest of the bar is empty, whenever I click this bar musescore crashes and closes. I've attached a screenshot of the offending bar.
| Attachment | Size |
|---|---|
| Screen Shot 2016-07-29 at 11.05.34.png | 28.98 KB |
Comments
That sounds and looks like a classic case of a corrupt measure. https://musescore.org/en/node/54721 should help you to fix it. Do you happen to have any idea how it got that way? It's definitely not supposed to happen.
In reply to That sounds and looks like a by Isaac Weiss
Thanks I'll give that a read now! It got that way because I had multimeasure rest turned on as I had a few bars of rests at the beginning. I added more bars along the way that turned into multimeasure and when I put a note in that started the problem.
Edit: I've fixed the problem with this from the link above!
"If MuseScore crashes while trying to select the bad measure, try instead selecting the measure immediately before or after the defective measure and then use Shift+→ or Shift+← as appropriate to expand the selection to include the defective measure. Once the measures are selected, you can use Ctrl+Del (Cmd+Del on Mac) to delete both measures and then follow the procedure to insert two new measures and input the notation information to correctly recreate the two measures deleted."
In reply to Thanks I'll give that a read by mattlawtonbass
Please attach your score (an image is almost useless) for checking what happens. And if you remember, provide precise steps (or good clues) to reproduce.
EDIT: By indicating the version used: 2.0.3 or earliers (2.0.2 etc.), and if the score was created with MuseScore, or imported first in another format (MIDI, MusicXML, others). Thanks.
In reply to Thanks I'll give that a read by mattlawtonbass
Glad you got it fixed! We recently got a report that sounds something like that: #119581: Select note values onto multimeasure rests in parts leads to corruption and crash. That issue has now been fixed for the next version of MuseScore. If that's not quite what happened to you, though, if you ever figure out exactly what steps introduced the corruption, we would very much appreciate you letting us know.