Glissando collides with elements before note

• May 4, 2013 - 11:26
S4 - Minor

1. Open attached score (produced in 1.3).

Result: Glissando collides with elements before the note.

Using MuseScore 2.0 Nightly Build (133dde1) - Mac 10.7.5.


Would you have a reference from a published score or another scorewriter to show this is an actual bug?

Sibelius 7

Attachment Size
06.png 61.53 KB

Page 141 of 'Behind Bars' explains: "A glissando line should not run through an accidental and risk obscuring it. Stop the line short of an accidental, or angle it to the left of the accidental".

chen lung: do you know of any rules for the distance from the end of glissando to the accidental?

If I just divide the width of the accidental I get the following:

Attachment Size
gliss.png 8.89 KB
Status (old) fixed active

Hi Soerboe

Thanks for your patch!

In some cases, it doesn't collide, but there's a few instances left.

1. Open attached score (produced in 1.3).
2. Move both notes up and down.

Result: Collisions with ledger lines and on the second note, accidentals.

Discussion: This maybe for another issue, but page 141 of 'Behind Bars' states: "The glissando line should follow the course of the pitches exactly. Angle it precisely between noteheads".

I asked David Bolton some questions:

"Do you have an opinion about glissando colliding with ledger lines?" David replied: "They should avoid colliding if possible".

"Should the glissando enter the space of the ledger line?" David replied: "Probably as long as it is not touching anything it would be okay".

Using MuseScore 2.0 Nightly Build (92852b7) - Mac 10.7.5.

Attachment Size
Collisions.mscz 1.43 KB

Ok, I'll look into it. Could you provide a picture from 'Behind Bars' of a "perfect" glissando? Preferably with some elements before the second note (if such a picture exists :) )

Status (old) patch (ready to commit) active

It might be a different report, but I noticed that the distance between the glissando and elements such as accidentals and note heads varies in the notes when changed up and down. Should it?

Using MuseScore 2.0 Nightly Build (aa8f987) - Mac 10.7.5.

Status (old) active fixed

@chenlung I guess you are refering to the squiggly line? this line is drawn with several times the "squiggly element" so except if we cut one of them, we can have an infinite number of distances but just a few (one element, two element etc...). And so the glissando is positionned in between the two notes for a integer number of squiggly element.

Status (old) fixed active

Thanks lasconic - I think I know what you mean.

A few more cases left I think - nearly there!

In the attached example (produced in 1.3), it collides with stems, ledger lines and accidentals.

In providing a solution, here are some things I've thought about:

Should the text of the glissando not appear?
Should the glissando be shorter?
Should the glissando be differently angled?
Should the space of the bar be wider?

Using MuseScore 2.0 Nightly Build (b61faaf) - Mac 10.7.5.

Attachment Size
Glissando.mscz 1.7 KB
Glissando.png 116.78 KB