Unexpected tieing behaviour
Reported version
3.4
Type
Functional
Frequency
Few
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
Input a note and press the tie button. Input another note to from a chord, then press tie button. The new note is tied, but the tie on the first note and the end note of that tie disappear. However, if you try a second time (press tie button when either note is selected), both notes are tied. Expected behaviour is to always tie all notes in a chord.
Comments
In this case, you want to use the command "Add tied note to chord". See https://musescore.org/en/handbook/ties#add-extra-tied-notes and #278752: New shortcut to add tied notes to a previously tied chord.
Or create the chord before pressing the tie button.
Expected behaviour is to always tie all notes in a chord.
You are right about this, though. The existing tie is preventing the regular tie command from working as expected. There should be no reason to have to use the alternate tie command. Specifically, these lines of code are causing the problem, and should probably be removed. It does not matter that the note already has a tie; we are overwriting any existing chord with a new chord, possibly of a different duration.
Removing those lines of code wasn't exactly the answer after all. For the regular tie command, any existing tie needs to be removed before the new tie is created. For the alternate tie command, existing ties can be preserved. See https://github.com/musescore/MuseScore/pull/5777.
For 3.x see https://github.com/musescore/MuseScore/pull/7871
Fixed in branch 3.x, commit 5d7314433c
_Fix #301768: Unexpected tieing behaviour
Resolves: https://musescore.org/en/node/301768
Backport of #5777_
For master see https://github.com/musescore/MuseScore/pull/7932 (rebased version of https://github.com/musescore/MuseScore/pull/5777)
Fixed in branch master, commit f198f8829b
_Fix #301768: Unexpected tieing behaviour
Resolves: https://musescore.org/en/node/301768.
Rebased version of #5777_
Automatically closed -- issue fixed for 2 weeks with no activity.