Rests interfere with re-pitching

• Feb 9, 2020 - 10:16
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project

Take the sample score, start re-pitching the chords from the first measure using keyboard. It works very well, for example, you can do this smoothly: C, Shift+D, E, Shift+F, and the two chords in the first measure will be replaced. But for the second measure, after pressing C, Shift+D, you have to pass the rest (by typing a pitch or 0) before re-pitching the second chord. This only happens to chords (with more than one note), because only after re-pitching a chord does the blue (or green, ...) rectangle fall back.

Attachment Size
Re-pitch.mscz 3.07 KB

Comments

"you have to pass the rest (by typing a pitch or 0)" ... or by pressing right arrow twice.

But what do think ought to happen? After repitching the first chord MuseScore doesn't know if you want to add another note to the cord, or move on and replace the rest with a note or move to the next chord to repitch that or do some other operation on it.

So,
step 1 - right arrow to end the repitching/add note to chord operation and move to the rest ready to enter a new note if that is what is wanted

step 2. right arrow to move to the next chord ready to repitch that.

All done with the keyboard. That seems to me to be a reasonable process. Or have I misunderstood your point?

In reply to by SteveBlower

I'm already using re-pitch mode, so I don't want to add note to a rest. And why should the behaviour be any different for single notes and chords? Pressing a pitch without Shift means going on to re-pitch the next chord, pressing with Shift means adding a note to the current chord. So either way MuseScore can know exactly what I want to do. Why should rest have anything to do with this process?