Only moved fret mark in tie moves tablature strings

• Aug 12, 2014 - 01:28
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

1. Open attached score (produced in 2.0).
2. Drag either fret mark towards another string.

Expected result: Both fret marks move.

Only dragged note in tie moves tablature strings (Expected result).png

Actual result: Only the dragged fret mark moves.

Only dragged note in tie moves tablature strings (Actual result).png

Using MuseScore 2.0 Nightly Build (88636cb) - Mac 10.7.5.

Attachment Size
Only dragged note in tie moves tablature strings.mscz 1.77 KB
Only dragged note in tie moves tablature strings (Expected result).png 10.11 KB
Only dragged note in tie moves tablature strings (Actual result).png 10.52 KB

Comments

• Aug 12, 2014 - 06:49

No, no, don't disable dragging, please! It's a "funny" and very intuitive feature.

1) It works very fine with slurs, it's perfect.

2) And, above all, for the ties, what interest of changing by dragging one of the two notes on an other string. Both notes are tied. This means that the sound is prolonged (!)

So, the finger must inevitably remain in place... on the same string!

That would be a mistake to do otherwise.

So it does not withstand scrutiny of instrumental practice.

Reply

• Aug 12, 2014 - 15:17

FWIW, I actually meant, maybe we could disable dragging for *notes*. It's never clear to me exactly how it should behave anyhow. But I'd never suggest disabling dragging for other markings.

Reply

• Aug 13, 2014 - 15:44

This maybe related:

1. Open attached score (produced in 2.0).
2. Click on the first fret mark of voice 1 (5).
3. Move down a string (Command Down)

Result: The voice 2 fret mark receiving the tie moves.

Moving fret mark to other string.png

Note: One fret mark of the tie continues to disconnect from the latter if step three is repeated.

Using MuseScore 2.0 Nightly Build (fc6a52a) - Mac 10.7.5.

Attachment Size
Moving fret mark to other string.mscz 2.05 KB
Moving fret mark to other string.png 68.44 KB

Reply

• Feb 25, 2015 - 11:21

Given the actual result is inconsistent, what would be the expected result?

A) Both tied notes are moved to the other string.

B) Only the dragged note is moved to the other string and the tie is removed.

My preference would be for A), but I'm not a guitarist.

Reply

• Feb 25, 2015 - 11:31

I re-checked the issue.

Keyboard command: if one of the tied notes are moved to another string via the relevant kbd command, it works as expected: both notes are moved to the new string and the tie keeps making sense.

Mouse dragging: if one of the tied notes is dragged with the mouse, the other note does not move and the tie become incongruous.

So, as far as I can see, this issue applies to mouse operations only. Working on it...

Reply

• Feb 25, 2015 - 23:51
Status (old) fixed ⇒ active

Hi

What is the behaviour now? Is dragging disabled for single-voice?

I've found a case where the bug remains - possibly only in multi-voice?:

1. Open this score (from #7).
2. Hold Shift until steps are finished.
3. Click-drag one of the frets (e.g. the first of the fifth fret).

Result: The other of the tied fret does not move.
Moving fret mark to other string - 2.png

Notes:

The augmentation dots and oblique stroke are wrongly placed.
After performing these steps, if you delete the receiving note, and extend the value of the first, the former will re-appear at the wrong fret.

Using MuseScore 2.0 Nightly Build 74ac9b5 - Mac 10.7.5.

Attachment Size
Moving fret mark to other string - 2.png 64.84 KB

Reply

• Feb 26, 2015 - 07:10

Dragging for single voice is NOT disabled; it should move the other tied note with itself.

If correctly understand your example, you are trying to drag a fret (either of the 5's) on a string which is already occupied; which is the expected result?

Note: In #7, you mention the keyboard command for changing string. Wasn't this discussion about dragging with the mouse?

Reply

• Feb 26, 2015 - 13:41

I cannot replicate #12 results from scratch. Starting from:

NOT FOUND: 1

I can drag either of the 10's to the third string:

NOT FOUND: 2

Then undo and drag either of the 5's to the third string again:

NOT FOUND: 3

It is not possible to drag the 5's to the second string, as it is already occupied. But is possible to drag the 14's to the 3rd line and then the 5's to the 2nd line. In all cases, dragging either of the tied notes, also moves the other.

The same results are obtained with the correspondent keyboard commands. What specifically is wrong with these dragging / moving operations?

Attachment Size
test_tab_drag_voices.png 3.32 KB
test_tab_drag_voices_2.png 3.32 KB
test_tab_drag_voices_3.png 3.25 KB

Reply

• Feb 26, 2015 - 20:37
Title Only dragged fret mark in tie moves tablature strings ⇒ Only moved fret mark in tie moves tablature strings

Indeed, dragging isn't disabled for voice 1 - I tried another score too.

About the bug listed in #7:

It is still reproducible for me - as well as #12.

I'm not actually sure what the expected result should be - what do you think? Even if you move the Voice 2 content away (down some strings) from Voice 1, the problem still occurs.

I thought this maybe related, but the title probably is misleading (only applied to original issue) - changing it.

Reply

• Feb 27, 2015 - 00:30
Status (old) active ⇒ needs info

I tried the score in #7, quoted in #12 as well, and I am rather sure it is corrupted: both ties in the TAB staff point internally to the '10' note in the second measure rather than one to the '5' and one to the '10' (as it can be ascertained in the debugger).

If, with current master code, the ties are deleted and re-entered (I tried to re-enter them either in the standard staff and in the TAB staff), then everything works as expected.

As far as I can tell, the issue is fixed, but please do your own tests!

Reply

• Feb 28, 2015 - 00:32
Status (old) needs info ⇒ fixed

Yes, the score probably is corrupt. Hmm…

Thanks for your investigations - I will mark as fixed.

Using MuseScore 2.0 Nightly Build 561cae3 - Mac 10.7.5.

Reply