2018-05-31 6:03 GMT+02:00 Rick Kimpel <rick.kim...@outlook.com>:
> From: Thomas Morley <thomasmorle...@gmail.com>
> Your sample works in 2.18, as well. I did notice that the gliss line can
> obscure the dot. Interestingly, my workaround does something that
> confuses the dot and puts it above the squiggle. Can't decide if that's the
> best way to go, or if I should force the gliss to start after the dot.
> bound-details.left.padding would do the trick there.
The optional argument of \durLine is supposed to serve for that purpose.
> I couldn't figure out why you had to override the to-barline. Also, your
> TODO about that is crazy. I was really surprised by the results of leaving it
> out. ?!
The idea of durLine was to insert grace-notes right after the end of
it's musical argument.
Something like:
{
<c' c''>1
\grace <c' c''>1
}
Then insert \glissando and make all stuff related to the graces
invisible or point-stencils or omit it at all, only keeping the
glissando.
As viewable by the tiny code above the graces may appear in the next bar.
Causing some disadvantages.
If you want to insert stuff like breaks, other bar-lines, key- or
meter-changes etc at the beginning of this bar you need a second voice
and care about grace-synchronisation:
\new Staff
<<
{
<c' c''>1\glissando
\grace <c' c''>1
s1
}
{
s1
\key d \major
\bar ":..:"
\time 2/2
\grace s1
s1
}
>>
Also this example demonstrates why setting 'to-barline is preferable
there, if it would work as desired ...
I've no clue why the glissandi-slopes are messed up.
Here a minimal example causing the attached image. I lean towards
calling it a bug.
{
\once \override Glissando.to-barline = ##t
<c' c''>1\glissando
<c' c''>1
}
Cheers,
Harm
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
