Cannot save online due to supposed "incomplete measure" where repeat measure sign used
When trying to save online the attached mscz, musescore refuses to because of corrupted measures:
Measure 60 Staff 4 incomplete. Expected: 4/4; Found: 0/1
Measure 61 Staff 4 incomplete. Expected: 4/4; Found: 0/1
... and so on for all the next measures with %'s.
The attached png shows meas 59, which has a simple rhythm in staff 4, and meas 60, which has a repeat measure sign (%) in staff 4. I ended up deleting those repeat measure signs, and then it is able to save online. But interestingly enough, musescore does not complain about another similar pattern of a repeat measure sign after a measure of drum rhythm earlier in the score. And even if I delete the rhythm in meas 59, it still complains. So I'm having difficulties identifying what the underlying problem is, and am unable to write a useful bug report untill I can.
(note: currently on arch linux 2.0.1)
| Attachment | Size |
|---|---|
| cannot-save-online-because-says-staff4-repeat-measure-does-not-have-4beats.png | 76.12 KB |
| Mega_Man_2_incomplete.mscz | 41.54 KB |
Comments
Check https://musescore.org/en/node/54721
In reply to Check by Jojo-Schmitz
Thanks. For some reason it saves online now ok. But I can't remember the exact steps I have done to fix the suspect measure, and don't know how that measure was corrupted in the first place.
In reply to Thanks. For some reason it by ericfontainejazz
(I'm wondering if maybe the simple act of saving the score to disk, restarting musescore, and reopening the score somehow fixed that measure.)
In reply to (I'm wondering if maybe the by ericfontainejazz
Sometimes it is that simple ;-)
In reply to Check by Jojo-Schmitz
(FWIW, I made the score entirely in musescore 2.0 releases, while your link is referring to importing earlier scores into 2.0)
Did you perhaps post the wrong version of the file? That one loaded just fine for me, and I was also able to save it online just fine.
EDIT: ok, odd, somehow the previus responses weren't showing up for me at first.
Anyhow, the instructions on fixing corruptions are general, they aren't specific to fixing the corruptions that happened in 1.3. There are just a lot more 1.3 scores out there that potentially need fixing, so maybe that's why things are worded as they are.
In reply to Did you perhaps post the by Marc Sabatella
Indeed, that corrupted score became safe the moment that I saved it to disk and reopened.
But I have found a way to reproduce the "corruption":
1. Open the mscz attached to this comment.
Note: this score will be able to save online.
2. Change measure 60 staff 4 into a repeat measure sign (%).
Now this score is corrupted and will NOT save online.
3. Optionally save this "corrupted" to score to disk and reopen.
Now this score is no longer corrupted and will save online.
In reply to Indeed, that corrupted score by ericfontainejazz
I'm confirming these steps create corruption both on Windows 8.1 (2.0.1 b25f81d) and Arch linux (2.0.1 3543170)
In reply to I'm confirming these steps by ericfontainejazz
I can confirm in a current development build as well. It's not unique to this score, either. Start with a blank score, add a repeat measure symbol from the Repeats palette anywhere, then try tio save online. It will be reported as corrupt. Save / reload and all is well. I have submitted an official bug report: #64506: Repeat measure reports as corrupt when saving online, corrects itself on save / reload.