delete range first notes keeps key but add accidentals ??
How to reproduce:
new score, key with 2 sharps, enter F notes in the first 2 measures, ctrl-del the first 3 notes => D key still there (2 sharps) but F's in the score have accidental #
I could understand D key disappearing by ctrl-del first notes and F getting accidental F#; or key preserved and no accidental on F. But current behaviour seems a strange mixture to me.
| Attachment | Size |
|---|---|
| test.mscz | 4.86 KB |
Comments
I can confirm, but only by ctrl+del each note separately - i.e., one by one.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.5.2.311459983, revision: 465e7b6
In reply to I can confirm, but only by… by Jm6stringer
I did a range delete (of the first 3 notes).
Now my score seems really corrupted by that simple action: if I undo lot of times to come back to the very original empty score, F sounds natural in the first measure?!?
In reply to I can confirm, but only by… by Jm6stringer
I get the same results as Jm6stringer. I also found that if you use down arrow then up arrow or 2 up arrows it's as though the key signature is ignored. Reapplying the key signature seems to fix it. Definitely a bug.
I've definitely seen this happen too, clearly a bug but I hadn't bothered to figured out the precise steps to reproduce. Re-adding the key signatures fixes it, so workaround is simple. I also suspect the file would be fixed on save/reload, as I am guessing the problem is the internal key signature "map" has become out of sync with the actual score.