Re: Turn lead sheet into a blank staff

Hi Sandro, > I'm producing lead sheets with lyrics, melody and chords > and would like to extract from them som blank sheets with > just lyrics and chords so that players can take their notes > onto (for solos or arrangements). Maybe there’s something helpful in

Re: Turn lead sheet into a blank staff

Hi, I'm trying with a custom \hide command, defined as follows: hide = { \override NoteHead #'transparent = ##t \override Stem #'transparent = ##t \override TupletBracket #'bracket-visibility = ##f \override TupletNumber #'stencil = ##f \override Accidental #'transpa

Turn lead sheet into a blank staff

I'm producing lead sheets with lyrics, melody and chords and would like to extract from them som blank sheets with just lyrics and chords so that players can take their notes onto (for solos or arrangements). My first attempt has been with using \hideNotes but that one still keeps some elements (c

Re: Problem with linebreaks and musicglyphs (lyuser: message 1 of 20)

Hello Schneidy and noeck, Thanks, both answers are very helpful and work beautifully :) cu -- Markus Grunwald ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Problem with linebreaks and musicglyphs

Dear Markus, there are probably other solutions that center the coda glyphs and the dash more elegantly, but this works. \line combines several markup-parts into one line: \relative c'' { c c ^\markup{ \center-column { "D.S." "Nach der 2. Str." \line { \musicglyph #"scri

Re: Problem with linebreaks and musicglyphs

Hi Markus, How about: \version "2.18.2" \relative c'' { c c ^\markup \override #'(baseline-skip . 2) % <= possibly \center-column { "D.S." "Nach der 2. Str." \line\vcenter { \musicglyph #"scripts.coda" - \musicglyph #"scripts.coda" } } c } Cheers, Pierre -- Sent from: http:/

Problem with linebreaks and musicglyphs

Hello, Consider this example: \version "2.18.2" \relative c'' { c c ^\markup{\center-column {"D.S." "Nach der 2. Str." "Coda - Coda"}} c } It's /almost/ what I want, except that I'd like to have the glyph \musicglyph #"scripts.coda" instead of the "Coda" string. I don't know how to put that...

Re: Arrows indicating split/combined voices (aka snippet #650) overlapping TimSignature changes

On 2019-04-03 1:01 am, Michael Gerdau wrote: in the Snippet Repository there is under number 650 (http://lsr.di.unimi.it/LSR/Snippet?id=650) a rather neat snippet showing splitting and converging arrows for voices. However with increasing frequency I'm encountering timesignature changes where the

Re: Adding parallel thirds to the notes of a melody

On 2019-04-02 11:15 pm, Gianmaria Lari wrote: The following "test" function adds parallel thirds to the notes of a melody: \version "2.21.0" scale = {c d e f g a b} test = #(define-music-function (music) (ly:music?) #{ \partCombine $music \modalTranspose c e \scale $music #}) \test

Re: How to retain string numbers when using `q` chord repeater?

Il giorno mer 3 apr 2019 alle 0:30, Stig Brautaset ha scritto: I've got this score: \version "2.19.82" \new TabStaff { q } It results in the following tab, which is not what I want: :--- :To- :A--4--- :B--4-4- :---2-2- :--- Is there any way to retain the fingering from the

Arrows indicating split/combined voices (aka snippet #650) overlapping TimSignature changes

Hi List, in the Snippet Repository there is under number 650 (http://lsr.di.unimi.it/LSR/Snippet?id=650) a rather neat snippet showing splitting and converging arrows for voices. However with increasing frequency I'm encountering timesignature changes where these splits occur. In those cases t

Re: Adding parallel thirds to the notes of a melody

At 07:15 on 03 Apr 2019, Gianmaria Lari wrote: > The following "test" function adds parallel thirds to the notes of a > melody: > > \version "2.21.0" > scale = {c d e f g a b} > test = > #(define-music-function (music) (ly:music?) >#{ > \partCombine $music \modalTranspose c e \scale $mus

Re: Adding parallel thirds to the notes of a melody

On 4/3/19, Gianmaria Lari wrote: > I don't have lilypond programming experience and I would like to know: > - if there are hidden mistakes No, that’s quite clean actually! > - if it is better to write the function in a different way I think in this case, simpler is better. > - how I could avoi