Bug : after changing layout from 0.70 to 1.0, extra clefs and key signatures get added 3 measures ahead

• Jun 5, 2020 - 10:42

See
https://www.youtube.com/watch?v=iiu3J32lRNU&feature=youtu.be

Edit: the video isn't great. The Microsoft game capture tool only captures the main window and doesn't show the other window when I select the measure, right click, select "Measure properties", and change "Layout stretch" from 0.70 to 1.0 .

Not sure if this is known . I have run into this a few times. The extra clefs can be deleted.

The extra key signatures are harder to get rid of : I had to first mark them invisible, then visible again, before I could delete them.

Attachment Size
Harmonious_Blacksmith_test_case_2.mscz 49.63 KB

Comments

• Jun 5, 2020 - 17:27

Was this score perhaps originally created in an older version of MuseScore, say, something around 3.0 - 3.1? There were a couple known bug that were fixed a year or more ago, but scores that were already "infected" by the bug would still show its effects later.

I see also this seems to have been originally imported from MusicXML, that could possibly have something to do with it. The original file would probably help in investigating.

What's happened, in a nutshell, is that the clef & key somehow got marked as not being a normal part of the system header - they are being treated as if you had inserted an actual clef and key change there. Understanding how that happened would be the key. Right now MuseScore is doing what it is supposed to do with this score given that it marked that way; the bug was the fact that the score got into this state to begin with. So those are the steps we'd need.

BTW, in the future, please write out steps to reproduce a problem, it's far easier to follow than a video in most cases.

Reply

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