Changing key signature of one staff doesn't work
Windows 10, MS 3.2.3
Please see measure 16 of the attached mscz, which corresponds to the double bar/key change of the attached PNG.
The clarinet key signature is 6 flats in the mscz (happened automatically when the key of the concert pitch instruments was changed to 3 flats), while the desired engraving is in the enharmonic equivalent of 6 sharps.
Attempting to make the mscz match the PNG-
1) CTRL+Select the 6 sharps icon from the Key Signatures palette and drag it onto the A clarinet 6 flats key signature at measure 16.
Expected outcome: the 6 flats changes to 6 sharps.
Actual outcome: the 6 flats changes to 3 sharps.
Maybe this is operator error? If it's an actual bug, I would appreciate any work-arounds or other advice.
As a possible work-around, should I just leave the mscz in 6 flats and continue transcribing?
Thanks,
| Attachment | Size |
|---|---|
| Yeletsky's_Aria.mscz | 23.23 KB |
| Capture.PNG | 107.86 KB |
Comments
This is by design - adding a key signature always works in concert pitch.
Unfortunately we don't currently have a good way to force a particular enharmonic spelling for keys upon transposition. People have come up with clever workarounds involving Tools / Transpose, maybe someone will be able to suggest something that works here (my first couple of attempts did not).
In reply to This is by design - adding a… by Marc Sabatella
Marc, thanks for the info. Wasn't there a recent forum issue re: A and Bb clarinets; I believe you said the A was best in sharp key signatures, and Bb in flats? I assume that's why the engraver went with the enharmonic equivalent in this case.
In reply to Marc, thanks for the info… by marty strasinger
Well, no, not quite. For one thing, the instrument doesn't care if the key is written as F# or Gb, it's going to sound the same. That's more about what is perceived to be easier for the player to read (and it's a tossup). But more to the point, when I say the A clarinet sounds better in sharp keys, I mean, concert sharp keys. The key of A concert is the single best key for A clarinet, because it works out to be C major written, meaning you play the entire scale without needing any of the side keys and get the truest intonation (in theory). The key of Eb concert - which is what you have there - is probably the single worst key for A clarinet, because it is as far removed from A concert on the circle of fifths as you can get. This is the point of the piece where one might strongly consider switching to Bb clarinet, actually.
In reply to Well, no, not quite. For… by Marc Sabatella
Well that's an idea- shift it to Bb, with an editors note that the original score leaves the instrument as an A clarinet.
In reply to Well that's an idea- shift… by marty strasinger
I'd only suggest this if it is truly practical - if the passage in question is long enough to make the switch worthwhile, and there is time before and after to make the switch, etc.
In reply to I'd only suggest this if it… by Marc Sabatella
It turns out there is one note later in the score that is too low for the Bb clarinet.
So, I stuck with the A clarinet, and the 6 flats key signature, with an editorial note that the original score is in the enharmonic equivalent of 6 sharps, not 6 flats, at the key change.
I could probably have made the 6 flats key sig not visible, and dropped a 6 sharps PNG on top of it, and then put non-visible accidentals in front of all the notes to make it work. But not worth the effort to me.
Is MuseScore's inability to provide the desired key signature something that is just too difficult to revise in the code? Should I submit a Feature Request, or is there already one in place?
In reply to It turns out there is one… by marty strasinger
It's something that is already on the radar, see for instance #288495: Allow user to select flats or sharps for enharmonic key signatures and #39176: Option to convert transposed instrument key signatures into enharmonic equivalent when number of accidentals exceeds limit. I don't think it's particularly hard to implement controls over this, the hold is really about deciding the best way to present the option tot he user (a checkbox specific to the key signature in the Inspector? a staff property? score style setting? some combination?)