Undo and transpose (concert pitch) changes key signature

• Mar 10, 2013 - 04:40
Type
Functional
Severity
S2 - Critical
Status
closed
Project

Steps to reproduce bug
1. Create new score for Bb trumpet
2. Switch to Concert Pitch
3. Edit > Undo

Expected behavior: The score switches back to a transposing score and the Concert Pitch button updates to reflect this fact

Actual behavior: The key signature changes but MuseScore still thinks it is in Concert Pitch (the button state does not change).

Discussion: Marked as critical because the steps cause MuseScore to forget the correct key signature for transposing instruments. For a single staff with no key changes a it is easy to restore the correct key signature (if the user notices it is wrong). But for multi-staff scores with multiple key changes, manual correction is more involved and error prone.

MuseScore version: 26ae8aa

(Operating System: Windows 7)


Comments

Title Undo and transpose changes key signature Undo and transpose (concert pitch) changes key signature
Status (old) duplicate active

Not at actually fixed yet:

Steps to reproduce bug
1. Create new score for Bb trumpet
2. Switch to Concert Pitch
3. Edit > Undo
4. Click Concert Pitch again

Expected behavior: Key should be C major again.

Actual behavior: Key is Bb major (two flats).

The bug you describe in comment #3 is a duplicate of http://musescore.org/en/node/16506:

When trying to undo a transposition, the key signature is not correctly restored.
Since changing "Concert Pitch" state is (internally) done by a transpose command, trying to undo a "Concert Pitch" change also results in the same problem. In your case (comment #3):

Step 2: Switching to "Concert Pitch" results in a 'transpose major second down'. (D maj -> C maj)
Step 3: Undo gets back the original notes, but not the original key signature. (See my comment #2 in issue 16506)
Step 4: Switching to "Concert Pitch" again does a 'transpose major second down'. Since we're still in C maj, we get Bb maj.

I think we should close this issue, because the original description doesn't show a bug and #3 is already filed.