Adding erroneous accidental marks

• Sep 20, 2020 - 16:30
Reported version
S4 - Minor
needs info

1) Select a chord, say a tri-tone.
2) Use arrow key to change pitch of the chord.
3) Notice that MS3 has likely added an accidental mark that does not match the chord. This is insidious and has resulted in a lot of time on my part hunting to find all the instances of this error. It is infuriating to discover these errors well after the fact of their commission. IT doesn't seem to happen all the time, unfortunately.
The workaround is to carefully watch any change of a chord and manually verify and revert notes of the chord into proper tone as frequently required
This has resulted in an embarrassing situation with a pianist who was just paying what was written.
It's seriously irritating to have to put up with this bug. At this point I consider the error to be of type Major because MS3 is generating the incorrect music with a valid input when processing a valid use case.

Best regards.


Severity S3 - Major S4 - Minor
Status active needs info

You really need to put these complaints into the bug and support forum located at first. What you are describing sounds like it's by design. Programmers are responsive to legitimate bugs but it sounds like you need help using the program.

To be clear: the inteded effect of pressing the arrow keys is to change the pitch of the selected notes by a semitone. This does indeed often involve adding an accidental. Selecting a chord consisting of B and F, for example, then pressing "Up", should produce C and F# (or, depending on the key, perhaps Bx and F#, or C and Gb). Accidentals will be added to make sure the notation is correct according to these pitches and the state of the key signature and previous accidentals in the measure. This is all normal and correct.

So, if you have some specific score and a precise set of steps in which you find that the pitch is not simply being raised a semitone, or where the notation does not match the actual pitch, please attach the score and those precise steps so we can investigate. I suspect, however, it will turn out to be a misunderstanding, as a basic flaw like this would not likely have passed unnoticed all these years!