Glissando too short from grace note to the first note of a measure in TAB
Type
Functional
Frequency
Few
Severity
S3 - Major
Status
active
Regression
No
Workaround
No
Project
1. Open attached score (produced in 15f1850).
Result: Glissando is barely visible.
Using MuseScore 2.0 Nightly Build 15f1850 - Mac 10.7.5.
| Attachment | Size |
|---|---|
| Glissando between grace and normal notes not always visible.mscz | 3.9 KB |
| Glissando between grace and normal notes not always visible.png | 43.12 KB |
Comments
Regarding the expected result, the glissando should be visible (maybe there isn't enough space being allocated, or it's being masked?). However, I'm not certain about its presentation - should the angle of the glissando not exceed the height of the grace note fret mark? What about the case of grace after?
(I forgot that it seems to only apply to tablature.)
I've just realised that it is visible sometimes, but I don't know why (attached score saved in nightly listed below):
![Glissando between grace and normal notes in tablature not always visible.png]( "Glissando between grace and normal notes in tablature not always visible.png")
Using MuseScore 2.0 Nightly Build 15f1850 - Mac 10.7.5.
Seems like extra room is allocated for the glissando unless it's the first note of the measure.
On a pitched stave, it is the opposite, somewhat (see attached score - produced in 1.3): Too much space is being allocated prior to the grace note - the culprit seems to be the glissando (if removed, the notes will move to the left - similar to the potential result below).
Potential result (approximate. Taken from 1.3):
![Space allocated prior to grace note with glissando - Potential result.png]()
Actual result:
![Space allocated prior to grace note with glissando - Actual result.png]()
Using MuseScore 2.0 Nightly Build 482db33 - Mac 10.7.5.
(Thanks to Marc for his assistance on this.)
Updating the title to reflect the addition of the issue in #4 - it seems to only occur at the beginning of a system, rather than at the start of a bar.
#4 is expected; not great, but at the moment rather difficult to avoid.
It depends on the fact that the graces are positioned with respect to the chord they belong to and, if the chord is moved to allocate more space for the glissando (which happens primarily at system beginning) the grace(s) will move with it.
There is a symmetrical issue with after-graces, which are positioned as far right as possible: if a glissando is inserted between an after-grace and the following chord, any additional space for the glissando is 'eaten' by the grace, which simply move more to the right.
As glissando between grace notes is not *SO* frequent, I would imagine these are not going to be fixed any soon and would be probably better left to manual adjustments.
I'll check if the worse-looking layout in tabs can be improved or is exactly the same things as in std staves.
The basic idea is to mark it as "Postponed", if not even as "Won't fix it".
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.5.0.13199, revision: 43c5553
Still an issue. Open the attached score. The discrepancy between glissandos at the start of the standard staff and tablature is very apparent:
![glissandos_grace_note.png]( "glissandos_grace_note.png")
Related to #310776: [EPIC] Grace note issues
See also #286672: Glissando too short from grace note to the first note of a measure in TAB (duplicate).