Regression: no key signatures at beginning of systems if any instrument is unpitched percussion
461d30b, create a new score that includes an unpitched percussion instrument along with any pitched instrument, and any key signature other than C/a. Result: the key signature appears at the beginning of the first system, but not on any subsequent ones.
Comments
The case is seemed to happen along with the issue #271260: Incorrect Clef position on appending percussion instruments, so that if Clef position is incorrect, key signatures are also missed.
The child of #271331: [EPIC] Positioning, symbols, notation related issues
I think the incorrect clef position has more to do with the number of lines in the staff. There should not be a key signature for the unpitched instruments, but the pitched instruments should have key signatures on every system. This issue occurs even when the clef position for the unpitched instrument is correct, which is the case for a Drumset, which has 5 staff lines.
See https://github.com/musescore/MuseScore/pull/3623.
Hmm, seems this is not restricted to unpitched percussion, but happens also with 'My First Score" (Piano, treble staff), but only with that ?!?
Edit: no this is #271066: Affected range not updated after key change
Actually, this is a very specific issue regarding how the presence of an unpitched instrument can disable KeySig segments for all other staves. Indeed, there are other issues involving key signatures and clefs, and I have submitted patches for many of them.
Fixed in branch master, commit 4b602d1489
fix #140256: Regression: no key signatures at beginning of systems if any instrument is unpitched percussion
Fixed in branch master, commit d357f58b5d
Merge pull request #3623 from mattmcclinch/140256-keysig-unpitched
fix #140256: Regression: no key signatures at beginning of systems if…
Automatically closed -- issue fixed for 2 weeks with no activity.