Sorry I was in a hurry few minutes ago and I simply copy/paste an old
coding.
Well, having some more time and re-reading the code I've seen some minor
things:
\version "2.19.35"
%%% Credit to the LSR => http://lsr.di.unimi.it/LSR/Item?id=82
#(define (add-gliss m)
(case (ly:music-property m 'na
Sorry, too fast:
#(define (add-gliss m)
(case (ly:music-property m 'name)
((NoteEvent) (set! (ly:music-property m 'articulations)
(append (ly:music-property m 'articulations)
(list (make-music (quote GlissandoEvent)
m)
2016-01-27 19:38 GMT+01:00 Caio Giovaneti de Barros :
Well, you can see that this code is much bigger than mine.
>
Yep, plus some copy/paste errors. So here again:
\version "2.19.32"
#(define path-gliss
(lambda (grob)
(if (ly:stencil? (ly:line-spanner::print grob))
(let* ((stenc
Well, you can see that this code is much bigger than mine. I'm a bit
uncomfortable because I don't have yet the lilypond-scheme vocabulary to
understand it.
OTOH, it has a more convenient syntax, not needing to add a \glissando
in every note. It should be a good solution for longer passages. I
Hi Caio,
How about:
\version "2.19.35"
#(define path-gliss
(lambda (handle)
(lambda (grob)
(if (ly:stencil? (ly:line-spanner::print grob))
(let* ((stencil (ly:line-spanner::print grob))
(X-ext (ly:stencil-extent stencil X))
(Y-ext (ly:stencil-extent stencil Y))
I think I got it. It's a bit of an ugly code, but works.
\version "2.19.35"
\relative c' {
\override NoteHead.stencil = #ly:text-interface::print
\override NoteHead.text = \markup { \null }
\override NoteHead.stem-attachment = #'(0 . 0)
\override Glissando.thickness = #5
\override Glissand
I'm trying to draw a suggestion for glissando in changing directions.
The ideal notation would be beamed stems without note heads connected by
glissandi. Here's what I got so far:
\version "2.19.35"
\relative c' {
\override NoteHead.stem-attachment = #'(0 . 0)
\hide NoteHead
\override Glis
