Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MU3] Fix #314696: Ties end at wrong note #7155

Merged
merged 1 commit into from
Dec 28, 2020

Conversation

mattmcclinch
Copy link
Contributor

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.

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.
@mattmcclinch
Copy link
Contributor Author

mattmcclinch commented Dec 30, 2020

This worked to fix the original example, but it does not fix the latest example posted to the issue thread. In fact, it makes it worse. I may take another look at what might be done to solve this issue of importing ties from certain 2.x scores, but I think the first step is to revert this change. Truth be told, it was definitely a hack, and not a good one at that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants