UI for setting mode with key signature doesn't function properly
Reported version
3.3
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
No
Project
System info
OS: macOS 10.14, Arch.: x86_64, MuseScore version (64-bit): 3.3.0.23833 (3.3 RC), revision: d3bff12
Steps to reproduce
- Create a new score with a non-null key signature (that is, not C major or neutral key).
- Select the initial key signature in the editing window.
- In the Inspector, choose a mode other than "unknown".
Expected result
The selected mode should be applied to the key signature.
Actual result
The mode remains "unknown". There appears to be no way to apply a mode to the initial key signature without hand-editing the MSCX data. Applying a mode to a key signature later in the piece appears to work as expected.
This is somewhat related to #271505: Allow user to set mode along with key signature.
Fix version
4.0.0
Comments
I can confirm this. If you enter an initial key signature besides C, you can select any instrument's key signature (like the Bb clarinet's) and change the mode, which will be applied to all instruments. If the key signature is C Major, you cannot do this. Selecting the Bb clarinets 2 sharps, changing the mode and reselecting the key signature returns the mode to unknown.
I have managed to find a workaround. Set the key signature to something besides C major in the first measure, in the second measure set the Key signature to C major. Select the key signature (including accidentals on a C instrument) and set the mode. Delete the first measure and the mode will remain. The accidentals also disappear, but the word for the mode is blue to indicate only some key signatures have a mode assigned. Since this does not work the way it's supposed to I agree the severity should be major.
In reply to I can confirm this. If you… by mike320
I'm not sure I understand how that comment is relevant to this issue. Did you mean to be responding to #295911: MusicXML export strips key signatures with 0 accidentals? Or is this a different mode bug?
In reply to I can confirm this. If you… by mike320
[deleted duplicate post]
On rereading, I guess there is a workaround...
In reply to On rereading, I guess there… by marnen
...except I just tried the workaround and it doesn't work for me. Oy.
I guess the workaround is only for scores with transposing instruments. I don't know if it would store the mode info in the score without it. If there is a transposing instrument, you can select it's key signature but there isn't one in scores like a string quartet or piano solo. This makes the workaround conditional.
In reply to I guess the workaround is… by mike320
Yeah, that could be. Right now I'm running into this on leadsheets, where there's only one staff and it's in concert pitch.
I found this too.
This bug is still present in 3.6.1. I have to hand-edit the MSCX file to get the mode to take.
Does'nt change where it got first reported
And of course this is still in 3.6.1, that's why this issue is still active
In reply to (No subject) by Jojo-Schmitz
Still present in 4.0 too, but interestingly it only affects the initial key signature at the start of the score - it works fine for other key signatures added after the beginning. You don't even need to save/reload to see the problem, just deselecting then re-selecting the clef is enough to see it's forgotten the mode setting.
Related issue is that if your initial key signature is C major, there's no way to select it and make it "A minor" that I can determine.
In reply to Still present in 4.0 too,… by Dylan Nicholson1
Also MU3 doesn't let you change these properties for "auto-generated" key-signatures shown at the start of each system. MU4 doesn't but it only applies the change to the auto-generated signature rather than the main one, which certainly doesn't seem right. Not sure what the best behaviour there would be.
See #304086: Cannot save the Key Signature Mode