Corruption in a saved part after a change of time signature
All 3/4 Files created on musescore are not being opened. An error message shows up saying that the expected measure is 4/4... When ignored the sheet music will appear properly, but when played there is a hidden rest that is being played. Then when the 3/4 time signature is attached, there will be a quarter note that will appear.
Attachment | Size |
---|---|
Screenshot (6).png | 1.04 MB |
Screenshot (7).png | 118.43 KB |
Screenshot (8).png | 128.28 KB |
Glory_to_God.mscz | 26.02 KB |
Comments
follow the instructions you'll find here: https://musescore.org/en/node/54721
Perhaps, for help, it is best to use the forum https://musescore.org/en/forum/6
welcome.
it seems ok now?
The question is, how did the score get into this state? It should not normally be possible. Deleting a time signature should convert everything to 4/4.
Well, found a new avatar involving the immediate creation of parts, followed by a time signature change, and by the removal of a score portion, of which the first measure, that mean the disappearance of the time signature in the part.
See: #89401: Deletion of the first measure removes the time signature in parts
If you save this part, you find exactly the result reported initially by the user.
- Steps to reproduce (77e980d / Windows 8.1)
1) New score for organ, 4/4 TimeSig
2) Fill some measures with different note values (but whatever), or open this test file:
organ test.mscz
3) Generate parts (and only for the display, delete the third staff via "I")
4) Change of time signature to 3/4
5) Delete (Ctrl + Del) the first measure in main score
6) View Part: result: no timesig (it is not a surprise now)
7) Press "M" to disable mmrests (for the display, too) and save this Part ie:
Save under -> Save -> Close
8) Reload this score/part (file test at this step: organ.mscz )
Result: corruption warnings
Notes:
- If you look at the end of the piece, you see the same double end barlines, like on the attached file by the user, this one for recall: Glory_to_God.mscz
- And if you add a 3/4 timesig, rests appear (no surprise too), as also described initially.
I am not understanding step 3 - could you explain what you mean? I tried viewing the part, pressing I, deleting the third staff (which, btw, is known to cause other problems - deleting a staff if linked parts exist for that instrument). I also don't understand the "save" step - do you mean you want to save the part only, without the score?
It seems step 3 might not be relevant - it's really just about saving the part that is missing the time signature causing corruption, because at that point it's in 3/4 but the lack of time signature cause MuseScore to think it is 4/4?
If so, then this is a duplicate of #89401: Deletion of the first measure removes the time signature in parts. Fixing that means the time signature won't be deleted, so there will be no corruption warnings on load because MuseScore will know the score is in 3/.4 rather than thinking it is in 4.4, and there glitch with the double bar lines does not happen either.
So if I am understanding correctly, we can close this.
Forget this deletion of third staff. Not involved at all in this issue. So, new steps:
1) "My First Score"
2) Enter notes in a few measures
3) Generate parts -> Ok
4) Change time signature to 3/4
5) Delete the first measure in main score
6) View part
7) (You are always in this part): File -> Save under -> Save, and close
8) Reload this saved part
Result: corruption warning (expected: 4/4, found: 3/4 or other), and so, at the opening, a really corrupted score!
Great, then in that case, it is indeed a duplicate. Scores without time signatures are allowed but are always assumed to be 4/4. So the bug is that we allowed a score to have no time signature even though it is not 4/4, and that bug is #89401: Deletion of the first measure removes the time signature in parts.
Ok, we have now identified an important source of corruption with this bug #89401: Deletion of the first measure removes the time signature in parts
I thought, of course, to a duplicate, but the result of corruption in a saved part had not been yet noticed, and I wanted to be sure that your pending fix will resolve this issue. If this is the case, it's perfect.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.