Key signatures behave weirdly after switching from an unpitched instrument to a pitched one
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.2.548021803, revision: 3224f34
I think this could be seen as one or more issues, but I'm not 100% sure, so I'll post here first. Below is some introduction for context, but the actual bug is described at point 3.
Percussion players (in concert bands, for instance) often need to switch between pitched and unpitched instruments. Support for switching between percussion clef and treble clef was, I believe, recently added, which is fantastic news for orchestra composers! However, it still causes a few problems.
The attached score shows two different approaches a MuseScore user could take when writing for a percussionist that needs to switch between Vibraphone and Concert Bass Drum, in two different orders:
(a) Playing vibraphone first, then bass drum; using the Concert Bass Drum instrument
(b) Playing vibraphone first, then bass drum; using the generic Percussion instrument
(c) Playing bass drum first, then vibraphone; using the Concert Bass Drum instrument
(d) Playing bass drum first, then vibraphone; using the generic Percussion instrument
Each approach has its issues, which makes such a piece impossible to write without the hassle of creating multiple staves for the same person. Some of these make sense, but it would be great if there was at least one way that actually, completely works.
1. Switching between 1- and 5-line notation is impossible, meaning (a) shows the bass drum on the wrong line and (c) makes the vibraphone impossible to read.
2. (c) and (d) don't add a treble clef automatically when switching to Vibraphone. Note that the treble clef still does not appear on the next system. Can be fixed by simpy manually adding the clef.
3. The main problem: key signatures behave weirdly after switching from an unpitched instrument to a pitched one. It seems like unpitched instruments are always set to C or - if there used to be a pitched instrument on the same staff - the previous key.
- Try adding a key change to bar 3. The effects show on (c) and (d), but the new key is never shown, not even on the next system. (a) and (b) ignore the new key in bar 5.
- Try adding a key change to bar 4. Three sharps appear on the end of the first system, implying that we're modulating to the key we're already in. Again, (a) and (b) ignore the new key in bar 5.
- Adding a key change to bar 5 works as intended.
Because of problem 3, even option (b) doesn't completely work. Any workarounds are welcome (except the ones where I just add extra instruments and click "Hide empty staves").
Attachment | Size |
---|---|
PercProblem.mscz | 17.14 KB |
Comments
Did you add the instrument change from the pallet or from the Add>Text Menu? If you did it from the pallet then I think you may be experiencing this bug #320828: Change Instrument Palette Text does not recognise current instrument leading to incorrect transpositions And see also https://musescore.org/en/node/329567
Workaround is to add instrument and changes from the Add>Text menu.
In reply to Did you add the instrument… by SteveBlower
Interesting, but this does not fix the problem: this new score shows the same behaviour, but the instrument change was added from Add>Text.
In reply to Interesting, but this does… by Teun Buwalda
Yes. it seems you are experiencing a different problem (or problems). There has been a lot of weirdness around instrument changes and transpositions that has been fixed, but users are still finding new examples.
Regarding point 1, you can add a staff type change (only available in the text pallet) which allows you to set the number of lines. Unfortunately, a single line corresponds to the top line of a 5 line stave rather than the middle line which I think is what you would really want.
In reply to Yes. it seems you are… by SteveBlower
I didn't know about staff type changes, I believe that does (at least partly) fix point 1! Thank you.
In reply to Interesting, but this does… by Teun Buwalda
It looks like bug. Could You report this issue on github?
In reply to Interesting, but this does… by Teun Buwalda
Workround could be to add local key signature after change to pitched percusion.
In reply to Workround could be to add… by sammik
I feel like I tried this in a different score, but I can't quite remember the results. Anyway, it works in the second file I attached above.
Not sure if this is related, but adding a local key signature in bar 6 of PercProblem.mscz also causes some odd behaviour: whatever key signature I add to the bottom staff holding Ctrl, there will also always be 4 flats appearing in the top staff, even though those are already present in the earlier measure.
In reply to I feel like I tried this in… by Teun Buwalda
I am not sure, if I understand.
I tested Your file and it works, see
In reply to I am not sure, if I… by sammik
The bug might have to do with the fact that I had a system break between measures 4 and 5. If I add that break, the extra flats appear again, and removing it doesn't fix the problem. But maybe this thread is getting off-track.
In reply to The bug might have to do… by Teun Buwalda
Ah, now I see.
It seems to me, it is another bug - percussion shouldnt have key signature at all, but if user changes instrument to Percusiion, it has key signature next system (at least).
I think, this should be reported to gihtub as well.
In reply to The bug might have to do… by Teun Buwalda
Workround is adding local Open key signature one bar before Change instrument to precussion and make it invisible. You also need to make accidentals invisible in that bar.
In reply to The bug might have to do… by Teun Buwalda
I think, I found much better workround.
Add "Staff type change" (it is in Text palette" on place, where Instrument change is.