MuseScore icon indicating copy to clipboard operation
MuseScore copied to clipboard

Key signatures of transposed instruments

Open oscardssmith opened this issue 2 years ago • 13 comments

Adding a key signature to a solo piece for an instrument that isn't in concert pitch adds a key signature in concert pitch. I'm not sure what the right behavior is when dragging a key signature into a score with multiple instruments that are in different keys, but it's really confusing as a user to drag a key signature with 2 sharps into a clarinet part and see 4 sharps.

oscardssmith avatar Dec 17 '22 23:12 oscardssmith

This doesn't strike me as an issue, but more a matter of user preference - just add a C Major key signature for two sharps in a Bb clarinet? Or compose in concert pitch, then transpose the whole score down a Major Second?

eitanmuir avatar Dec 18 '22 00:12 eitanmuir

Unfortunately this is probably one where desired behavior depends on background, but as a woodwind player, I am much more likely to think in instrument pitch than concert pitch. This definitely isn't a massive issue, but it's just one that requires an extra couple seconds of thought whenever you change key signatures.

oscardssmith avatar Dec 18 '22 00:12 oscardssmith

Next time, for issues, we encourage you to follow this:).

Though I understand your issue. When you create a score for a transposed instrument, say B-flat clarinet, we start with the key of D, because C-major in concert pitch is D-major for a B-flat clarinet (their D sounds like a concert C). The key signatures in the palette are also in concert pitch, so dropping them onto the score will give their transposed counterparts.

Whether this should be the intended behavior is up to question, and I'd agree that this should not be the behavior for transposed solo instruments.

quinnouyang avatar Dec 18 '22 00:12 quinnouyang

"but as a woodwind player, I am much more likely to think in instrument pitch than concert pitch."

Welcome to transposing instruments 😃

As a woodwind player too I do think the same usually, but this is not the case, when you see a clarinet sonata in Eb major you don't see clarinet having an Eb major signature, can't see why this shouldn't be the same even when there's no other instruments.

Additionally, I think it would be a little problematic or confusing for new users who don't know much about how transposing instruments work and hear their solo clarinet is playing in Db instead of Eb or when they later add an instrument in C and notice the key signature has 5 flats when they initially chose 3

Fristover avatar Dec 18 '22 01:12 Fristover

The reason it is done this way is because otherwise the behavior is undefined when you have a score for mixed transpositions - if you select D major in a score for orchestra, how should MuseScore know which D major you meant? The only sensible thing is to treat key signatures as concert in that case. And then having it work differently depending on how many instruments happen to be included would be inconsistent and would look like a bug.

MarcSabatella avatar Dec 18 '22 05:12 MarcSabatella

if you select D major in a score for orchestra, how should MuseScore know which D major you meant?

It could be done this way:

  • if You drop into transposed instrument, MS ads keysig in instrument pitch
  • if You drop into normal instrument, MS ads keysig in concert pitch
  • if multiple staves with different transposing (and normal) isnstruments are selcted, MS ads keysig in concert pitch

sammik avatar Dec 18 '22 11:12 sammik

Ehh, I really don't think that's a good idea, the way it works now it's just fine, they're transposing instruments so you should think of them as that

Fristover avatar Dec 18 '22 11:12 Fristover

I agree, it's possible to design in inconsistent interface that attempts to "do what I mean", and hope users can guess which behavior they'll get from any given action. I think it better to keep it consistent personally, then no one needs to guess.

MarcSabatella avatar Dec 18 '22 14:12 MarcSabatella

I agree, it's possible to design in inconsistent interface that attempts to "do what I mean", and hope users can guess which behavior they'll get from any given action. I think it better to keep it consistent personally, then no one needs to guess.

It is not "inconsistent". It has just different rules ("add always in concert pitch" vs "add in selected instrument pitch").

(I would leave it, as it is now, but it is not true, "is not possible do it other way".)

sammik avatar Dec 18 '22 14:12 sammik

Think if someone dragging to the score, not particularly thinking about which staff their mouse happens to be closest to when they release the mouse. It would look random to them. Or if they just happen to click a measure before clicking the key signature without thinking about what its transposition is.

I’m not saying it’s impossible to make up an algorithm, but I am saying, it’s likely to generate surprise a lot of the time and not feel like an improvement as a result.

MarcSabatella avatar Dec 18 '22 17:12 MarcSabatella

Well, than more rigid rule could be: add in instrument pitch, if there is (are) only instrument(s) only that pitch. (which is actually original request here)

But yes, it is a bit ad hoc rule.

sammik avatar Dec 18 '22 17:12 sammik

I just realised one more context - note input mode.

Key stroke "c" always creates written note C - if score is in concert pitch, it creates C note in concert pitch, if score is in transposed pitch, it creates written C, which is not (sounding) C.

sammik avatar Dec 19 '22 21:12 sammik

Certainly, but in that context it is 100% clear and obvious the pitch refers to the staff you are entering the note on. There is no such thing as entering a note for the entire score the way there is for key signatures. So, there really isn't much to the analogy, as the case that explains why key signatures are always concert pitch simply cannot exist in note input mode.

MarcSabatella avatar Dec 19 '22 22:12 MarcSabatella