We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
In imported MS3 scores, the ties in tablature are positioned too high.
To Reproduce
Steps to reproduce the behavior:
Open the attahched MS3 file (in zip file). auber - fd_on_yonder_rock_(hayden).mscz.zip
Look at the ties in tablature, measures 3 and 9.
RESULT: The ties are positioned too high.
Expected behavior
The ties should be positioned at approx the same vertical level as in MS3.
Platform information
OS: Linux Mint 20.1, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-2059995262, revision: github-musescore-musescore-cafefd7
The text was updated successfully, but these errors were encountered:
Hi! @rgreen5 Do you have the same difference as I have (attached to the description) ?
Sorry, something went wrong.
FYI @oktophonie
Hi! @rgreen5 Do you have the same difference as I have (attached to the description)?
Yes, the same.
Merge pull request #11508 from asattely/slurs-in-tab-height
b904f87
Fix #10991 Fix ties for tab staves
oktophonie
asattely
Successfully merging a pull request may close this issue.
Describe the bug
In imported MS3 scores, the ties in tablature are positioned too high.
To Reproduce
Steps to reproduce the behavior:
Open the attahched MS3 file (in zip file).
auber - fd_on_yonder_rock_(hayden).mscz.zip
Look at the ties in tablature, measures 3 and 9.
RESULT: The ties are positioned too high.
Expected behavior
The ties should be positioned at approx the same vertical level as in MS3.
Platform information
OS: Linux Mint 20.1, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-2059995262, revision: github-musescore-musescore-cafefd7
The text was updated successfully, but these errors were encountered: