Glissando Confusion
In the attached score, a new section begins at measure 23, and rightly belongs on a new page. There are glissandos in the piano and guitar parts leading into the new section from measure 22. The problem is that the glissandos lead off at an angle towards the position of the notes on the new page, while they should be leading to where the gliss would end if the measures were directly contiguous. (shouldn't they?) Both glissandos visually lead the players UP, while in fact, they should be leading down. (In the case of the piano, three octaves down.) In both cases, the performers would be very confused by the direction of the lines.
This is not a bug. It is a result of the way MuseScore deals with two opposing/incompatible tasks - drawing gliss lines, and formatting line/page breaks. MuseScore hunts for the target note to end the gliss and draws a line in that direction, rather than where the target note would be sans page break.
The easiest way to avoid this is to force the page break to a different measure, but as I stated at the outset, the new section rightly belongs on its own page. Is there another way to fix this?
| Attachment | Size |
|---|---|
| 2-04 Peaches n Cream - Dance MS3.mscz | 128.53 KB |
Comments
Move gliss anchor points:
In reply to Move gliss anchor points: … by Jm6stringer
I feel dumb! I thought I had tried this. (Whatever I tried did not survive the import from MS2 to MS3.) It appears that when lines cross a break, MuseScore treats the two halves as separate entities. (That is a good thing.)
I suppose it would be too much to wish that MuseScore could figure that out on its own when lines cross a break.
Thanks so much!
In reply to I feel dumb! I thought I had… by toffle
I suppose it would be too much to wish that MuseScore could figure that out on its own when lines cross a break.
In this particular case...
The additional challenge for 'figuring it out' automatically is that the topmost (lead guitar) staff vanishes at the break (empty staves are hidden).
This causes all the other staves to move up to fill the void, so they are no longer horizontally aligned across pages 6 & 7.
In reply to I suppose it would be too… by Jm6stringer
"This causes all the other staves to move up to fill the void, so they are no longer horizontally aligned across pages 6 & 7."
The question is, should this even make a difference? "Hide empty staves" has quite a long history in MuseScore. Surely there is a way to predict and adjust how this might have an impact on a function such as drawing glissandos.
In reply to "This causes all the other… by toffle
Drawing glissandos has been problematic as long as I can remember. When they cross systems they are always drawn in a manner that they will point the line to where the note is physically on the page rather than where it should be on the staff relative to where it starts.
In reply to Drawing glissandos has been… by mike320
I was going to say something similar in my initial description, but got hung up on the fact that until you print it, it’s not “physically” anywhere. I thought about that for awhile, then had to go have a nap.
On another note, it’s good to know that it’s easy to fix manually, but it would also be very nice if it could be something MuseScore recognizes when a system or page break disrupts the drawing of a line.