Glissandos collide with double-digit start fretmarks in tablature
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.4.2.9788, revision: 148e43f
This has been an issue since the year dot. In MuseScore standard staves, glissandos have a small amount of space on either side to prevent collision with start and end notes:
However, in tablature this space has not been properly implemented:
If there is a double figure at the start, there is a collision:
Probably, this is connected with #110981: Glissandos not centred between notes in tablature.
Fix version
3.6.0
Comments
Actually, this goes back to MS 2.3.2.
The issue tracker doesn't though
Relates to #311175: [EPIC] Engraving issues and suggestions
Reported again at #311728: Tablature glissando with numbers greater than 9 overlap.
Relates to #270551: [EPIC] Tablature issues.
After seeing that my issue was a duplicate, I decided to take a look at the code, I notice that there's no specific instance of tab-width but that the code only deals with the "notehead" width. If I merely add a line of code to reset the x-offsetting to take into consideration the "tab" width only on the first (left most) position of the glissando when on a tab-staff, it seems to fix the issue. I'll do a PR and hope some will be willing to further test it.
https://github.com/musescore/MuseScore/pull/6680
And also #110981: Glissandos not centred between notes in tablature?
Fixed in branch 3.x, commit 179865ac0e
Fix #309322: Glissandos collide with double-digit start fretmarks
Fixed in branch 3.x, commit 9eec9dbe3e
Fix #309322: Glissandos collide with double-digit start fretmarks
In reply to And also #110981: Glissandos… by geetar
@geetar, please test out a nightly branch now, as this PR i put together includes updating the alignment of the glissando lines besides making sure they don't clash with double-digits. Left-sided and Right-sided portion of the lines should be equivalent now. If you catch anything funny, post a comment etc, but it should be okay.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.0.395303918, revision: github-musescore-musescore-
Looks fine.
Automatically closed -- issue fixed for 2 weeks with no activity.