[Regression] Unable to start slur mode (within note input) one voice > 1 at end of measure

• May 21, 2019 - 03:17
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
MuseScore

When entering the notes in this picture

no slur 2.PNG

Enter the top, tied notes in voice 1 and the notes in voice 2 with the following key strokes

n
ctrl+alt+2
6
b
s
d

The slur is not entered into the score. It is necessary to go back and enter it after exiting note input mode.

Comments

• May 21, 2019 - 14:57
Title [Regression] Slur not permitted in voice 2 when voice 1 has tie ⇒ [Regression] Slur cannot be entered in note input mode in voice 2 when voice 1 has tie

Reply

• May 21, 2019 - 17:18

The tie is irrelevant. So is the status of note input mode. If there is no chord or rest in voice 2 to serve as the slur's endElement, then the slur will not be created.

Reply

• May 21, 2019 - 17:44
Title [Regression] Slur cannot be entered in note input mode in voice 2 when voice 1 has tie ⇒ [Regression] Unable to start slur mode (within note input) one voice > 1 at end of measure

The tie is indeed irrelevant, but note input mode is not. It is supposed to be possible to enter "slur mode", where after pressing "S", subsequent notes get slurred to the previous note automatically. And it works fine in 2.3.2, and in most cases in 3.x. It just seems to fail if you try to start slur mode while at the end of a measure, unless indeed there is already a note or rest in the next measure in that voice.

So, a simpler way to reproduce the bug:

1) empty 4/4 measure
2) note input
3) voice 2
4) C D E F, then "S", then G

Result: G is not tied to the F.

Reply

• May 21, 2019 - 18:13

I should have left mscore/scoreview.cpp:3148 alone, then. The change to line 3113 was sufficient to fix the related issue. (Line numbers as they appear in PR #4077, that is.)

Reply

Fix version
3.1.0