Re: Several questions concerning scheme-music-function

On 2018-05-26 06:15, Robert Schmaus wrote: so far, I was completely satisfied with out-of-the box lilypond and rarely used anything involving scheme. Mainly because, I find this language very counter-intuitive, but that's maybe because I code in C-like languages all the time. Hi Robert, This

RE: hairpins ignored on chords

Crimson, May I call you Crimson? This worked for me, is it what you want? \version "2.19.81" \score{ { \clef "bass" <\parenthesize f->~ f,~ >2\> 8\! r8 r4 } } Mark From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of

Re: hairpins ignored on chords

crimsonsunr...@protonmail.com writes: > I tested this on 2.18.2, 2.19.48 and 2.21.0. None print the crescendo > or decrescendo haripins, no matter where you put them. It also doesn't > warn or complain about anything: > > \score{ > { > \clef "bass" > } > > Is there a way to make it work? They

hairpins ignored on chords

I tested this on 2.18.2, 2.19.48 and 2.21.0. None print the crescendo or decrescendo haripins, no matter where you put them. It also doesn't warn or complain about anything: \score{ { \clef "bass" <\parenthesize f->~ f,~\> >2 8 r8 r4 } Is there a way to make it

Re: Several questions concerning scheme-music-function

Robert Schmaus writes: > Dear Ponderers, > > so far, I was completely satisfied with out-of-the box lilypond and > rarely used anything involving scheme. Mainly because, I find this > language very counter-intuitive, but that's maybe because I code in > C-like languages

Several questions concerning scheme-music-function

Dear Ponderers, so far, I was completely satisfied with out-of-the box lilypond and rarely used anything involving scheme. Mainly because, I find this language very counter-intuitive, but that's maybe because I code in C-like languages all the time. Anyway, my project was to make me a

Re: \path and \postscript in staff

Am 25.05.2018 um 13:13 schrieb Thomas Morley: > Hi, > > you'll need a spanner from note to note, Glissando is your best bet, I'd say. > I once made the attached code. Wow! That solves the problem. This fancy glissando can be fine tuned for each instrument, so that it produces nearly the picture

Re: \path and \postscript in staff

Am 25.05.2018 um 13:44 schrieb Aaron Hill: > On 2018-05-24 23:15, Helge Kruse wrote: >> But these lines are outside the staff. If you change "(rlineto 10 1)" to >> "(rlineto 10 10)" then the starting point is moved down to keep the >> markup outside the stuff. Further it doesn't support the