I was out a while and am finally getting caught up I believe this is indeed a bug. I could see the algorithm needing to consider the whole measure (it is mostly a "horizontal" algorithm, looking at preceding / following notes, not a "vertical" one), but it shouldn't alter what comes before. And it definitely shouldn't alter the previous measure. Looks like it is actually always doing the entire score. Looking at the sourc,e it seems no effort whatsoever is made to look at the selection.
I'd encourage you to submit this as an official bug report via Help / Report a Bug (set Severity to Major).
Help > Report a Bug is an option, at least in MuseScore 3.6.2 on Windows, it does lead to the issue tracker.
Anyway, apparently you found out how to do this, this issue here is the proof...
Comments
Comment by Marc Sabatella:
I was out a while and am finally getting caught up I believe this is indeed a bug. I could see the algorithm needing to consider the whole measure (it is mostly a "horizontal" algorithm, looking at preceding / following notes, not a "vertical" one), but it shouldn't alter what comes before. And it definitely shouldn't alter the previous measure. Looks like it is actually always doing the entire score. Looking at the sourc,e it seems no effort whatsoever is made to look at the selection.
I'd encourage you to submit this as an official bug report via Help / Report a Bug (set Severity to Major).
Had come up 2 more times before, and just today in the developers' chat on Discord
Only if there is no selection it might work on the entire score
Hi Marc
So sorry about this- I can't figure out how to report a bug.
If I select help, report a bug is not an option.
Warm regards,
Bill Rinehart, M. Mus.
billrinehart@me.com
www.jazzpianoonline.com
Help > Report a Bug is an option, at least in MuseScore 3.6.2 on Windows, it does lead to the issue tracker.
Anyway, apparently you found out how to do this, this issue here is the proof...
See https://github.com/musescore/MuseScore/pull/8775
PR got merged