Corruptions Starting to Happen Again, randomly...
There's a few issues I'd like to point out, but there's only one that's currently causing an actual issue that I'm unable to figure out...
Im stuck getting this message (the dreaded "corrupted score" warning that I was absolutely fed up with seeing and hoped I'd seen the last of it...). The message contents are as follows, copied from the popup window;
"The Score has Become Corrupted and Contains Errors"
"Incomplete measure: Part score: winds, measure 75, staff 9. Found: 6/4. Expected: 4/4."
"Incomplete measure: Part score: brass, measure 75, staff 9. Found: 6/4. Expected: 4/4."
While I appreciate that Musescore now actually highlights the measure corruption, problem is... I don't see a problem with it...
Visually it appears correct. Even selecting the individual notes, they indicate on the navigator in the bottom left corner that the note selection that corresponds with the beat it should be on is 100% correct. I've tried to rewrite the measure using copied contents from another staff in the same measure, but same issue reoccurs. Not too sure what to do here... [For Clarity, the score is in 4/4 or common time.]
Seems things like this only happen on larger scores (This one is nearly 9 minutes long, and is a full Symphony Orchestra rough draft...)
Comments
Since the problem is in the Winds and Brass parts, go to "Parts", click the ellipsis "..." in front of the name of these 2 parts, then click Reset. This should solve the problem.
In reply to Since the problem is in the… by cadiz1
Well, typically this would normally do it, however, it isn't in this case. I opted to delete the contents and write it back, from memory. This "fixed" it, however, the problem is reocurring, in so many different ways, and seemingly at random.
Another thing I notice often, is that random singular notes, in any staff, really, will automatically be raised by like 5-6 octaves without me having to do anything. Not sure what that could be either... not to mention how often a flute staff with a temporary piccolo part added to it via "change inst." function, ensuring the staff returns to the Flute later, after saving/closing/launching the score again, the notes will be written an octave higher than they're supposed to be, in the Piccolo section. Having to go back and fix these errors that aren't even of my own making tends to be a bit tedious sometimes... lol
> Visually it appears correct.
It looks like you are looking at the full score, but the problem is in Parts.
> "corrupted score" warning that I was absolutely fed up with seeing
Whenever you see a warning like this, it means that Musescore admits that it screwed up, brought the project to an invalid state and cannot fix it without human help (there are exceptions if the project was imported from pdf or musicxml, but I think that is not your case)
> Seems things like this only happen on larger scores
The issue is not in the size, in theory your issue can be reproduced in 1-2 pages, if we know how to do it.
> not to mention how often a flute staff with a temporary piccolo part > added to it via "change inst." function
The change instrument function is not the most frequently used and it is likely that many different issues are related to it.
If you want us to try to fix your project, attach the musescore file.
In reply to > Visually it appears… by mercuree
I understand. The issue is not present, at this time, and I no longer have the saved version in question, however, if these issues reappear, I will be sure to use the "save-as" function so I can have a copy for the forum.
In reply to > Visually it appears… by mercuree
edit: Also, the screenshot shown was viewing the score in the "Winds" part, not the full score tab.
When scoring, I usually create my own separate parts for each instrument section to simplify the process. (i.e. Create parts labeled "Winds" for woodwinds, "Brass", "Strings", "Percussion" and "Piano" (when used).
Not sure if the fact that the parts that show random corruptions were created manually would have anything to do with it, but figured that may be important context.