Key signature appears in multimeasure rest after being deleted from underlying measure

• Apr 8, 2019 - 22:30
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project

True in 3.0.5 and current master:

1) default score, or new score from treble template with system break after measure 4
2) add notes to measure 4
3) insert key signature at measure 5
4) "M" to enable mmrests
5) "M" to disable them again
6) delete keysig
7) "M" one more time

Result: keysig is back

Note also you cannot delete the keysig while mmrests are enabled, even before triggering this bug. That is, you should be able to delete the key signature form the mmrest after step 4, but you can't.

Key signatures are not current not linked between the underlying measures and the mmrests. Same with time signatures and clefs. There are a number of other subtle problems that could be solved by linking these - the non-generated ones, anyhow.

PR forthcoming.


Comments

Workaround No Yes

As a workaround, if you highlight the mmrest merged measure which shows the incorrect key signature, you can add a key signature to cancel out the incorrect one. In my case, D Major (two sharps) incorrectly appeared, and adding B-flat Major (two flats) caused the erroneous sharps to disappear, returning that measure's key signature to C Major. I did not do any additional testing of this workaround, but this worked for me.

OS: macOS Mojave (10.14), Arch.: x86_64, MuseScore version (64-bit): 3.0.5.21343, revision: 58dd23d

Status fixed active

I am reopening this issue because a similar problem can be observed by following mostly the same steps, but leaving measure 4 empty:

1) default score, or new score from treble template with system break after measure 4
2) insert key signature at measure 5
3) "M" to enable mmrests
4) "M" to disable them again
5) delete keysig
6) "M" one more time

The result looks like this:
mmrest.png

In a related matter, if you delete the system break after measure 4 (at step 5) and then reenable multimeasure rests, the system will still break at the same place, even though the system break element is gone.

Fix version
3.2.0