Transposing introduces redundant #'s and b's, but autocorrects after reload

• May 29, 2014 - 19:34
Type
Functional
Severity
S4 - Minor
Status
closed
Project

This issue was discussed in the forum. http://musescore.org/en/node/25899#comment-101677

I have a score in c-flat-major that I want to transpose to b-major. I.e., the tones don't change but all the notes change from the c-flat representation to the b representation.
I think the results are different than expected.

What I expect is that there are no # signs in the score. All of the notes are implicitly flat in the C-flat score (as c-flat has 7 flats), and 5 of the notes are sharp in the B score. But these should be implicit by the key signature. I don't want redundant shapes in the score after transposition.
I'm attaching screen shots of what I see before (c-flat-major) and after (b-major), as well as the values in the transpose form which I chose.
I"ll also attach the scores before and after.

Note that if you save the new score, and re-open it the redundant sharp signs vanish.


Comments

Title Transposing to enharmonic key signature doesn't work right away but after reload Transposing introduces redundant #'s and b's, but autocorrects after reload

I'm changing the title again. This problem is not limited to enharmonic keys. If I translate from B to Ab, it also fills up with extra sharp and natural signs.

Here is an example, starting with the score displayed in screen-shot-b, if I transpose it to Ab, you see that the notes translate correctly (in a sense) but there are lots of redundant flat and natural symbols. It is very ugly.

Attachment Size
screen-shot-b.png 342.23 KB
screen-shot-aflat.png 373.46 KB