Note entry for instruments tranposing by over an octave does not honor accidental state

• Jan 21, 2015 - 15:55
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

Ubuntu 14.04, GIT commit: 4516685

1) new score, tenor saxophone, key of F concert
2) verify concertn pitch is off; key displayed as G
3) note entry: B A Up B A

Result: the second "A" enters as an A natural - it doens't remember the A# entered earlier in the measure. However, if you repeat this but hit Ctrl+Down to after the second B to drop down an octave, *then* the second A is (incorrectly in this case) entered as an A#. The octave transposition is apparently confusing things, as it works fine for clarient, or if you switch to concert pitch.

Same thing happens for note entry by clicking on staff.

To be clear, there is no corruption or missing accidental or bad TPC or anything like that going on hear - the note entered works correctly for what it is. It's just not the note you were expecting to be entering.

Comments

• Jan 21, 2015 - 17:34
Status (old) active ⇒ patch (ready to commit)

https://github.com/musescore/MuseScore/pull/1661

BTW, This can also affect instruments that transpose by less than octave, it's just not always the case. You can also, with some effort, trigger another effect of the same underlying problem by deleting an accidental from certain notes (Cb, Cbb, B#, Bx) in transposing instruments and finding the effects not what you expect, although again, nothing corrupt or with playback out of sync with display or anything serious like that.

Reply