Ties end at wrong note

I can confirm this score loads differently in 3.x vs 2.x, but it isn't clear how it got into this state, but it seems the file itself may have confusing info (apparently conflicting tie and spanner id's, but I've forgotten the details about how the 2.x file format worked). Can you recreate this scenario from scratch?

There is an easy enough fix for this. See https://github.com/mattmcclinch/MuseScore/commit/9601417b1e05900032b091…. But I should point out that the bug is not in 3.x, but rather in how the 2.x score was written.

PR for 3.x branch is here: https://github.com/musescore/MuseScore/pull/7155.
PR for master branch is here: https://github.com/musescore/MuseScore/pull/7156.

Fixed in branch 3.x, commit b5a12163bc

_Fix #314696: Ties end at wrong note

Resolves: https://musescore.org/en/node/314696.

When reading the properties of a tied note from a 2.x score, check to see if the specified pitch matches the pitch of the note at the beginning of the tie. If the pitches do not match, then print a debug message to the console, and set the pitch of the new note to match the pitch of the starting note._

New pull request is here: https://github.com/musescore/MuseScore/pull/7190. It is a much better solution and it works with both examples.

Fixed in branch 3.x, commit 911f297345

_Revert "Fix #314696: Ties end at wrong note"

This reverts commit b5a12163bcad8a9204497a018c633a83d147c944._

Fixed in branch 3.x, commit 6f19008115

_Fix #314696: Ties end at wrong note

Resolves: https://musescore.org/en/node/314696._

(not in 3.6 RC though)

Fixed in branch master, commit 60c9ec4f4e

_Fix #314696: Ties end at wrong note

Resolves: https://musescore.org/en/node/314696._

Automatically closed -- issue fixed for 2 weeks with no activity.