Corrupt measures locked in parts, parts different from score

• Mar 14, 2023 - 14:35

Ms 4.02.23
MacBook Pro 2019 32 GB RAM, Intel chip
Ventura 13.2.1

Update: The fix for this was to go back to a previous score version, copy the affected instrument parts and paste them into the score on the score page. That worked. BUT...second time it's happened in 24 hours.

Problem description, file attached
My score is fine on the score page, but several parts show corruption. For example, for this score, m. 71 Elec. guitar 1, 2 & Elec Bass all state "measure 71, staff 1. Found: 0/1. Expected: 4/4.". The parts display properly in the score but in the part view this measure is empty and appear locked - that is, I can't paste in the proper notes from the score, nor can I click into the measure to hand-edit it.

I had this happen yesterday on another score so it doesn't appear isolated to just this score. I don't remember which or I'd include it too.

Score attached. Text of error messages:
Incomplete measure: Part score: Elec.Guit1, measure 71, staff 1. Found: 0/1. Expected: 4/4.
Incomplete measure: Part score: Elec.Guit2, measure 71, staff 1. Found: 0/1. Expected: 4/4.
Incomplete measure: Part score: ElecBass, measure 71, staff 1. Found: 0/1. Expected: 4/4.

File source was from musescore.com, it's been through multiple edit cycles including pasting parts from one version to another, although these three parts are pretty much untouched.

I had initially had another error:
Incomplete measure: Full score, measure 113, staff 3. Found: 19/16. Expected: 4/4.

which I was able to fix in the score and then paste in the correct notes. In this case notes showed in the part (Tmpt 3) but they were different from the score. Not sure how I unlocked the measure in the part, but I don't seem to be able to unlock m.71 in these parts.

Attachment Size
EyeTigerupdated.mscz 663.44 KB

Comments

Make sure you're on the current verison - 4.0.2 - as there were bugs in earlier versions that could occasionally created problems like this. Note you can easily fi this problem in the part by going to the Parts dialog, clicking the "..." menu for the part in question, and doing the reset.

If corruptions while whie using 4.0.2 (this should be much less likely), see if you can figure out precise steps to reproduce the crash, starting from an uncorrupted score. That would be the first step in being able to isolate and fix the problem. 4.0.2 makes detecting corruptions much simpler since you will be informed immediately upon saving, so you'll be more likely to remember the last things you did.

In reply to by Mrcake3014

You wrote that entire score from scratch within 4.0.2 just within the past 24 hours since it was released? Or maybe you mean, you had a score that didn't report corruption before, and now it does? That would be because previous versions simply weren't as good at reporting corruption, so lots of corruptions went undetected until now.

In reply to by Jojo-Schmitz

Yes, I had said that I downloaded it from Musescore.com. I've done extensive work on it, adding parts, transposing between instruments (e.g. taking the trumpet part and adding a F. horn and then pasting in the tot part. This is probably the 20th version more or less (guessing at a number, giving you an idea of the iterations). Tweaked some parts, replaced some portions of parts with other stuff. Did minor formatting stuff, added rehearsal marks, etc. The corruption appears to happen when I'm copy/pasting within an instrument part--eg I begin and everything is good, then after a couple of copy/pastes I get that corruption warning and the locked measure. The initial problem though - e. guitars & bass - were not caused by copy/paste within those parts. The subsequent Tpt part corruption did occur after I was directly working on uncorrupted parts.

In reply to by Marc Sabatella

Update:
Fixed by deleting TPT3, pasting in tpt2 part from earlier version. Evidently my interacting with the music caused the corruption. I was working in the part rather than main score, if that is relevant.

To update, I continued working on this score after the above fix (pasting unaffected parts into the corrupt score). I added 1 instrument:
Tpt3 as F. horn
and pasted the Tpt3 part into it.

Next I moved to Tpt 2 & 3 part and pasted some from tpt2 into tpt3 (m25 & 26) then decided I didn't want to do that, so deleted the notes and went to save. Got the following corruption message:

Incomplete measure: Full score, measure 25, staff 18. Found: 0/1. Expected: 4/4.
Incomplete measure: Full score, measure 26, staff 18. Found: 0/1. Expected: 4/4.
Incomplete measure: Part score: Trmp 2 & 3, measure 25, staff 2. Found: 0/1. Expected: 4/4.
Incomplete measure: Part score: Trmp 2 & 3, measure 26, staff 2. Found: 0/1. Expected: 4/4.
Incomplete measure: Part score: Trumpet 3, measure 25, staff 1. Found: 0/1. Expected: 4/4.
Incomplete measure: Part score: Trumpet 3, measure 26, staff 1. Found: 0/1. Expected: 4/4.

Reset from the PARTS dialogue ... didn't help. File attached.

Attachment Size
EyeTiger.mscz 702.52 KB

In reply to by Mrcake3014

Copying from another score that might also be corrupt will generally often copy the corruption too. And performing copy/paste operations within a score that is corrupted will often exacerbate the corruption. You need to fix the corruptions - and verify they are fixed by saving & reloading - before you can safely continue.

But if you're sure a) you have fixed all corruptions that currently exist in the score, and b) some sequence of steps introdcues a new corruption, then we'd need you to attach the score (both uncorrupted scores if the steps involving copying between uncorrupted scores) and give the precise steps to reproduce the corruption.

In reply to by Mrcake3014

So....I have questions.
The lists of instruments in the mixer, in the score, in Parts dialogue, and the generated parts, does agree in number or part name.
Trmp3 is hidden in the Instruments palette. It is one of the corrupted parts. If you don't need it, get rid of it. Same with trmpt 2,3.
Somewhere in the process of c+p sections of parts into other parts and the score, problems have come up. Gone undetected and multiplied. Lots of fun.

I opened your score in MU4, and closed all the parts. Exported as xml. Opened in MU3. saved as (new file name). Opened in MU4. No corruptions called out. However, trmpt 3 was still a problem in measure 25-26.

I can't tell how this problem occurs, and I'm not using MuS 4.x.
So I tried to open it in 3.6.2, and I could see in the electric guitar 2 and drums staff that there are completely empty mesaures. At least empty measures should have a whole rest! I think that's the problem. These measures are not even selectable. The cursor is pointing to such a measure.
MuseScore 3_ EyeTigerupdated_.png
I added additional staves for drums and electric guitar, and copied all the measures with regular notes - except for the measures that are completely empty - to the new staves. Then I deleted the original drum and guitar staves and all parts. The parts also contain these wrong measures.

Attached a 'repaired' version (MuS 3.6.2). This P.M. line for guitar 2 is missing ...

Attachment Size
EyeTigerupdated-3.6.2.mscz 65.14 KB

In reply to by HildeK

Thank you for this. I was able to fix my corrupt score by hand editing the uncompressed mscx file. For anyone else that might need help with this, here are some commands that might shed some light on the subject.

mkdir tmp
cd tmp
unzip ../broken.mscz
vim broken.mscx
(Make the fixes, save, exit)
zip -r ../fixed.mscz *
(Open fixed.mscz in Musescore and verify that there are no errors, close)
cd ..
rm -rf tmp
mv fixed.mscz broken.mscz

In reply to by chad.skeeters

Soluction

Problem:

The "incomplete measure" error was encountered in MuseScore.
The error occurred in measures 40 and 41 in the baritone, contralto, and tenor parts.
Solution:

Go to the "Parts" tab in MuseScore.
Click on the three dots (...) next to the part with the error (ex: baritone, contralto, and tenor).
Select the "Reset" option for the part with the error.
After resetting the part, the error should be corrected.
You can then edit the problematic measures without the program closing.
After the correction, the score can be saved successfully.
Please note that if you encounter similar errors in other parts, the same procedure can be used to correct them. This should resolve issues with corrupted measures in MuseScore.

Do you still have an unanswered question? Please log in first to post your question.