Can anyone tell me what this means and what I can do to fix it?
Can anyone tell me how to fix what they are telling me to fix? I would greatly appreciate it thanks!
Measure 17 Staff 7 incomplete. Expected: 4/4; Found: 26/24\nMeasure 17 Staff 8 incomplete. Expected: 4/4; Found: 26/24\nMeasure 37 Staff 1 incomplete. Expected: 4/4; Found: 15/16\nMeasure 38 Staff 2 incomplete. Expected: 4/4; Found: 15/16
Comments
This might arise when importing a score created with MuseScore 1.3 into version 2.0. It means that a few measures are corrupted—for example, a measure's duration is supposed to equal four quarter notes, but somehow it contains the equivalent of fifteen sixteenth notes, and with this much it's full.
Don't panic; it's easy to fix. Make a note of the corrupted measures (which you've already done). Click "Ignore" and load the score. Then go to each of the measures affected (using the schortcut Ctrl/Cmd+F and typing the measure number, then counting staves). Usually you can tell by looking at it that it just doesn't add up. Simply correct the note lengths and MuseScore 2.0 will recognize "Oh, that's right" and fix the measure.
MuseScore 1.3 would be unable to do this, and would stubbornly persist in keeping the measure at a length of 15/16. MuseScore 1.3, of course, would also create the corruption in the first place. MuseScore 2.0 is clever enough to realize there's something wrong and fix it when you put in something that makes sense.
I'm about to formalize this as a "How To " for the next person who comes along. Have fun!
In reply to This might arise when by Isaac Weiss
Oh thank you for the explanation how to put things right (I knew about the corruptions... but not how to change them well)
Could you also put the link when it is done ?
In reply to Oh thank you for the by Zynette
http://musescore.org/en/node/54721
In reply to http://musescore.org/en/node/ by Jojo-Schmitz
Hello,
I have seen your how to. The thing is: I cannot recognize anything that doesn't add up in the measures and staves called corrupt in my score:
Measure 24 Staff 2 incomplete. Expected: 4/8; Found: 12/16\nMeasure 24 Staff 6 incomplete. Expected: 4/8; Found: 12/16\nMeasure 28 Staff 6 incomplete. Expected: 4/8; Found: 9/16\nMeasure 43 Staff 6 incomplete. Expected: 4/8; Found: 1/8\nMeasure 43 Staff 7 incomplete. Expected: 4/8; Found: 7/16
My assumption is that MuseScore somehow adds cue notes, representing the Bandoneon voice that I added to the violin and the piano staves, to the violin and piano notes. Is that what you think as well?
If so, what do I need to do to NOT have those cue notes added in the counts? After all, they are just indicating what another voice is playing. The violin and piano notes do add up correctly to 4/8.
Thanks,
Peter
In reply to Hello, I have seen your how by pseller
Select measure 24 in 2,d or 6th staff and notice the colors indicating voices. Those cue notes look wrong, some belong to voice 1, some to voice 2, they should all be in voice 1 and the non-cue half note in voice 2, or vice versa.
In measure 28, staff 6 the notes in voice indeed 1 don't add up, I guess the 8th rest should be a 16th.
In measure 43, staff 7 indeed a 16th is missing, in staff 6 voice 1 (the cue note) is incomplete.
Voice 1 always needs to be complete, other voices don't need to (but of course are not allowed to contain more than voice 1)
In reply to Select measure 24 in 2,d or by Jojo-Schmitz
Thank you so much!
I overlooked that.
In reply to Hello, I have seen your how by pseller
The question now is, how did this happen? If it was that way in 1.3, chalk it up to a bug fixed long ago. Or if the score was created using one of the beta or earlier nightly builds, then I can still hope the bug that allowed this to happen is fixed. But if you just added those cue notes recently using 2.0, then there is a problem we need to understand and fix. Can you reproduce this problem?
In reply to This might arise when by Isaac Weiss
Thank you so much! Extremely helpful!
In reply to Thank you so much! Extremely by Poptsart
That's the highest praise I could possibly receive. ;-) Thank you, and you're very welcome.
I created the score using MuseScore 2.0 beta1 and possibly several nightly builds. My original input came from a PDF scan using PhotoScore 7 Ultimate.
I corrected the problem now in MuseScore 2.0, and I hope it won't reoccur. MuseScore 2.0 was the first version that gave the error message. Was this not checked in the nightly builds which were available in November and December?
In reply to I created the score using by pseller
Was this not checked in the nightly builds which were available in November and December?
Absolutely. This feature has been implemented in February: https://github.com/musescore/MuseScore/commit/924bcb94c6696137581ef0826…