Re: \RemoveEmptyStaves not removing first line

[Rohan Srinivasan]

Thank you - I meant to reply to the list. I have the following:

\version "2.19.82"

\header {
  title = "CLOUDS AND SUNSHINE"
  subtitle = "or, I'VE JUST ARRIVED FROM DIXIE"
  composer = "George H. Coes (1828?-1897)"
}

\paper {
  #(set-paper-size "a4")
}

\layout {
  \context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
  }
}

\layout {
  \context {
\Staff
\RemoveAllEmptyStaves
  }
}

paren =
#(define-event-function (parser location dyn) (ly:event?)
   (make-dynamic-script
#{ \markup \concat {
 \normal-text \italic \fontsize #2 (
\pad-x #0.2 #(ly:music-property dyn 'text)
\normal-text \italic \fontsize #2 )
   }
#}))

global = {
  \key f \major
  \numericTimeSignature
  \time 2/4
  \partial 8
}

sopranoVoice = \relative c'' {
  \global
  \dynamicUp
  r8 |
  R2*20

}

right = \relative c'' {
  \global
  \partial 8 c,8 |
  c c d8. e16 |
  f8 a r a |
  c[ b bes8. g16] |
  g4. c8 |
  \override DynamicLineSpanner.staff-padding = #3
  d16\f d c d a' g f d |
  c\paren\f c b c g' f c a |
  c\p c b c e d b g


}

left = \relative c' {
  \global
  \partial 8 r8 |
  \override Beam.damping = #1 f,,[  ] r |
  f,[  ] r |
  c,[  ] r |
  f,[  ] r |
  \undo \override Beam.damping = #1
  bes[  ] r | \break
  c,[  ] r |
  c,[  ] r |


}

sopranoVoicePart = \new Staff \with {
  instrumentName = ""
  \consists "Ambitus_engraver"
} { \sopranoVoice }

pianoPart = \new PianoStaff \with {
  instrumentName = ""
} <<
  \new Staff = "right" \right
  \new Staff = "left" { \clef bass \left }
>>

\score {
  <<
\sopranoVoicePart
\pianoPart
  >>
  \layout { }
}


On Wed, Oct 31, 2018 at 12:54 AM Lukas-Fabian Moser  wrote:

> (Replying to list, assuming you wrote to me personally only by accident,
> as implied by your wording):
> Am 31.10.18 um 00:42 schrieb Rohan Srinivasan:
>
> Could any of you give me an example of how \RemoveAllEmptyStaves is used?
> I have:
>
> \layout {
>   \context {
> \Staff
> \RemoveAllEmptyStaves
>   }
> }
>
> This still doesn't seem to clear the empty staves in the first system.
>
> Please always try to provide a compilable minimal example showing your
> problem.
>
> \version "2.19.80"
>
> \layout {
>   \context {
> \Staff
> \RemoveAllEmptyStaves
>   }
> }
>
> <<
>   \new Staff \with { instrumentName = "Voice" shortInstrumentName = "Voc"
> } { R1*30 \repeat unfold 80 c'4 }
>   \new PianoStaff \with { instrumentName = "Piano" shortInstrumentName =
> "Pn" } <<
> \new Staff { \repeat unfold 200 c'4 }
> \new Staff { \clef bass \repeat unfold 400 c8 }
>   >>
> >>
>
> works here:
>
> Best
> Lukas
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: BarNumber.whiteout over StaffGroup vertical lines

[Thomas Morley]

Am Mi., 31. Okt. 2018 um 19:09 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi there,
>
> Not sure if this is a bug or if I am using it wrong.
>
> I've started using :
> \consists "Mark_engraver"
> \consists "Bar_number_engraver"
> , etc
> inside StaffGroups since it is now working.
> (Fixed with I think 622cab6a34 (Thanks to Dan Eble))
>
> But I get a strange and inconsistent result with whiteouts of the
> Bar_number_engraver.
> The two images I've attached to this email are from a 400+ measures
> score. Sometimes the bar number is in front of the vertical system
> line and sometimes it is behind. I have not figured out what is
> different in each case as it pops-up rather anywhere.
>
> But! I have managed (by error) to "trigger" the behavior in the
> following MWE might you {un,}comment line 4.
>
> \version "2.21.0"
>
> music = \repeat unfold 7 {c'4}
> %music = \repeat unfold 8 {c'4}
>
> \score {
>   <<
> {s1 \break}
> \new StaffGroup \music
> \new StaffGroup \music
>   >>
>   \layout {
> \override Score.BarNumber.self-alignment-X = #CENTER
> \override Score.BarNumber.whiteout = #4
> \context {
>   \Score
>   \remove "Bar_number_engraver"
> }
> \context {
>   \StaffGroup
>   \consists "Bar_number_engraver"
> }
>   }
> }
>
> Should a bug report be filed?
>
> Thanks
> --
> Pierre-Luc Gauthier

Probably, BarNumber and SystemStartBar have the same layer. Try adding
  \override BarNumber.layer = 200
to StaffGroup-context.

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Spacing lyrics to avoid visible bar lines only

[Thomas Morley]

Am Mi., 31. Okt. 2018 um 18:11 Uhr schrieb joelhamme :
>
> My fellow singers in choir have been asking me to improve the visual chunking
> of choir staves. They wanted to have closed bar lines on the right edge of
> each choir staff.
>
> Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of clutter and
> results in collisions with the lyrics, which is particularly unappealing
> with thick repeat bars. This can be quickly fixed by adding `Bar_engraver`
> to `Lyrics` and hiding them as described in ^[notation lyrics].
>
> However, for aesthetical reasons I prefer removing all span bars, except
> non-defaults and single bar bars at the end of each line. So this would
> leave all repeats and double bar lines but no single bars unless there's a
> line break, much like ^[semi choir staff snippet]
>
> I've found a way to do this, except that there's some spacing issue with the
> lyrics at single bars that aren't even shown. In choir staves, lyrics can
> move below a bar line to take up the available space, which leaves a more
> pleasing appearance and saves space on the page. Sadly, I could either make
> the lyrics avoid all bar lines or not at all, but not only the ones that are
> actually shown.
>
> To the point:
> I would like to make the lyrics avoid some span bars while not avoiding the
> bar lines I've omitted using a call back.
>
> To illustrate I've compiled a somewhat minimal example using long words to
> trigger some collisions. For convenience I've also uploaded it to
> ^[lilybin].
>
> 
>
> ```lilypond
> \version "2.18.2"
>
> link = {
>   \once \override Score.RehearsalMark.self-alignment-X = #LEFT
>   \mark \markup \normalsize {
> \with-url #"http://lilybin.com/wmw4xx/6; "http://lilybin.com/wmw4xx/6;
>   }
> }
>
> redspn = \once \override Score.SpanBar.color = #red
> grnbar = \once \override Score.BarLine.color = #green
>
> notes = {
>   \link
>   c1 \redspn | \repeat volta 2 { c | c \grnbar | c } | c | c | c \bar "|."
> }
>
> words = \lyricmode {
>   Breathes | \markup { \with-color #red breathes } |
>   br | \markup { \with-color #green breathes } |
>   breathes | br | breathes |
> }
>
> \score {
>   \new ChoirStaff <<
> \new Staff \relative c'' \notes \addlyrics \words
> \new Staff \relative c'' \notes
>   >>
>
>   \layout {
> indent = 0
> \context { \ChoirStaff
>   \consists "Span_bar_engraver"
>   \override BarLine.after-line-breaking =
> #(lambda (grob)
>   (if
> (and (= 0 (ly:item-break-dir grob))
>  (string=? (ly:grob-property grob 'glyph-name) "|") )
> (ly:grob-set-property! grob 'allow-span-bar #f)))
> }
>
> % \context { \Lyrics
> % \consists "Bar_engraver"
> % \hide BarLine
> % \override BarLine.after-line-breaking =
> %   #(lambda (grob)
> % (if
> %   (and (= 0 (ly:item-break-dir grob)))
> %(string=? (ly:grob-property grob 'glyph-name) "|")
> %   (ly:grob-set-property! grob 'stencil #f))
> %   )
> % }
>   }
> }
> ```
>
> The red colour indicates an unacceptable collision, whereas the green colour
> indicates the desired loose spacing under bars that are not spanned across
> staves. The commented-out section removes the relevant bar line stencils
> from the lyrics, but fails to loosen the spacing where there are no longer
> any bars to avoid.
>
> Can I conditionally add bar lines to lyrics without otherwise affecting
> their spacing?
>
> Sorry this got so long, any help would be much appreciated.
>
> Cheers,
> Joel
>
> [notation lyrics]:
> http://lilypond.org/doc/v2.19/Documentation/notation/techniques-specific-to-lyrics#placing-syllables-horizontally
> [semi choir staff snippet]: http://lsr.di.unimi.it/LSR/Item?id=299
> [lilybin]: http://lilybin.com/wmw4xx/6

How about:

\version "2.18.2"

%% srfi-1 is not present inside \layout (needed for 'every')
%% Thus defined at toplevel
#(define set-extra-spacing-height-for-span-bars
  (lambda (grob)
(let* ((pap-col (ly:item-get-column grob))
   (nmpc (ly:grob-object pap-col 'left-neighbor))
   (nmpc-elts-array (ly:grob-object nmpc 'elements))
   (nmpc-elts-ls (if (ly:grob-array? nmpc-elts-array)
   (ly:grob-array->list nmpc-elts-array)
   '()))
   (sp-bl
 (filter
   (lambda (g) (grob::has-interface g 'span-bar-interface))
   nmpc-elts-ls))
   (sp-bl-glyphs
  (map (lambda (g) (ly:grob-property g 'glyph-name)) sp-bl)))
 (if (every (lambda (gl) (not (string=? "|" gl))) sp-bl-glyphs)
 '(-inf.0 . +inf.0)
 '(0 . 0)



link = {
  \once \override Score.RehearsalMark.self-alignment-X = #LEFT
  \mark \markup \normalsize {
\with-url #"http://lilybin.com/wmw4xx/6; "http://lilybin.com/wmw4xx/6;
  }
}

redspn = \once \override Score.SpanBar.color = #red
grnbar = \once 

Re: \RemoveEmptyStaves not removing first line

[Susan Buckingham]

Have also used the \override VerticalAxisGroup.remove-first = ##t and can
confirm this works with 2.18.2 when added to score block.

\score {
  <<
\flutePart
\pianoPart
  >>
  \layout { #(layout-set-staff-size 22)
 \context { \Staff \RemoveEmptyStaves
  \override VerticalAxisGroup.remove-first
= ##t }
   }
  \midi { }
}

On Mon, 29 Oct 2018 at 03:41, Malte Meyn  wrote:

>
>
> Am 29.10.18 um 05:52 schrieb Lukas-Fabian Moser:
> >
> >> I am currently engraving a song for soprano and piano which begins
> >> with 15 measures of piano solo. I would like the soprano's staff not
> >> to show since it is not playing. \RemoveEmptyStaves does not seem to
> >> hide the first line of the piece.
> >>
> > In current versions (there's no reason not to use the 2.19.xx
> > development versions which are stable enough for professional everyday
> > use), there's |\RemoveAllEmptyStaves| which does just that (like
> > \RemoveEmptyStaves but also remove the respective staves in the first
> > system).
>
> In 2.18.2 there is \override VerticalAxisGroup.remove-first = ##t for that.
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Spacing lyrics to avoid visible bar lines only

[Jan-Peter Voigt]

Hello Joel,

when I typeset choir scores, which I do most often, I use the
self-alignment-X override for long syllables:

words = \lyricmode {
  Breathes | \once \override LyricText.self-alignment-X = #-.5 \markup {
\with-color #red breathes } |
  br | \markup { \with-color #green breathes } |
  \once \override LyricText.self-alignment-X = #-.6 breathes | br |
breathes |
}

That harmonizes spacing. If you read some of my former posts you will
know I do inject those overrides with the edition-engraver because it
would be very tedious to place them alll inside the lyrics.
But with a small command
sax = #(define-music-function (parser location v)(number?) #{ \once
\override LyricText.self-alignment-X = #v #})

(or shorter in the V2.19 form - this doesn't work 2.18.2)
sax = \once \override LyricText.self-alignment-X = \etc

its not that much text, if you place them inside the lyrics:
   Breathes | \sax #-.5 \markup { \with-color #red breathes } |


I hope this small hint helps
Cheers,
Jan-Peter


Am 31.10.18 um 17:58 schrieb joelhamme:
> My fellow singers in choir have been asking me to improve the visual chunking
> of choir staves. They wanted to have closed bar lines on the right edge of
> each choir staff.
> 
> Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of clutter and
> results in collisions with the lyrics, which is particularly unappealing
> with thick repeat bars. This can be quickly fixed by adding `Bar_engraver`
> to `Lyrics` and hiding them as described in ^[notation lyrics].
> 
> However, for aesthetical reasons I prefer removing all span bars, except
> non-defaults and single bar bars at the end of each line. So this would
> leave all repeats and double bar lines but no single bars unless there's a
> line break, much like ^[semi choir staff snippet]
> 
> I've found a way to do this, except that there's some spacing issue with the
> lyrics at single bars that aren't even shown. In choir staves, lyrics can
> move below a bar line to take up the available space, which leaves a more
> pleasing appearance and saves space on the page. Sadly, I could either make
> the lyrics avoid all bar lines or not at all, but not only the ones that are
> actually shown.
> 
> To the point:
> I would like to make the lyrics avoid some span bars while not avoiding the
> bar lines I've omitted using a call back.
> 
> To illustrate I've compiled a somewhat minimal example using long words to
> trigger some collisions. For convenience I've also uploaded it to
> ^[lilybin].
> 
>  
> 
> ```lilypond
> \version "2.18.2"
> 
> link = {
>   \once \override Score.RehearsalMark.self-alignment-X = #LEFT
>   \mark \markup \normalsize {
>   \with-url #"http://lilybin.com/wmw4xx/6; "http://lilybin.com/wmw4xx/6;
>   }
> }
> 
> redspn = \once \override Score.SpanBar.color = #red
> grnbar = \once \override Score.BarLine.color = #green
> 
> notes = {
>   \link
>   c1 \redspn | \repeat volta 2 { c | c \grnbar | c } | c | c | c \bar "|."
> }
> 
> words = \lyricmode {
>   Breathes | \markup { \with-color #red breathes } |
>   br | \markup { \with-color #green breathes } |
>   breathes | br | breathes |
> }
> 
> \score {
>   \new ChoirStaff <<
> \new Staff \relative c'' \notes \addlyrics \words
> \new Staff \relative c'' \notes
>   >>
> 
>   \layout {
> indent = 0
> \context { \ChoirStaff
>   \consists "Span_bar_engraver"
>   \override BarLine.after-line-breaking =
> #(lambda (grob)
>   (if
> (and (= 0 (ly:item-break-dir grob))
>  (string=? (ly:grob-property grob 'glyph-name) "|") )
> (ly:grob-set-property! grob 'allow-span-bar #f)))
> }
>   
>   % \context { \Lyrics
> % \consists "Bar_engraver"
> % \hide BarLine
> % \override BarLine.after-line-breaking =
> %   #(lambda (grob)
> % (if
> %   (and (= 0 (ly:item-break-dir grob)))
> %(string=? (ly:grob-property grob 'glyph-name) "|")
> %   (ly:grob-set-property! grob 'stencil #f))
> %   )
> % }
>   }
> }
> ```
> 
> The red colour indicates an unacceptable collision, whereas the green colour
> indicates the desired loose spacing under bars that are not spanned across
> staves. The commented-out section removes the relevant bar line stencils
> from the lyrics, but fails to loosen the spacing where there are no longer
> any bars to avoid.
> 
> Can I conditionally add bar lines to lyrics without otherwise affecting
> their spacing?
> 
> Sorry this got so long, any help would be much appreciated.
> 
> Cheers,
> Joel
> 
> [notation lyrics]:
> http://lilypond.org/doc/v2.19/Documentation/notation/techniques-specific-to-lyrics#placing-syllables-horizontally
> [semi choir staff snippet]: http://lsr.di.unimi.it/LSR/Item?id=299
> [lilybin]: http://lilybin.com/wmw4xx/6
> 
> 
> 
> 
> --
> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
> 
> 

BarNumber.whiteout over StaffGroup vertical lines

[Pierre-Luc Gauthier]

Hi there,

Not sure if this is a bug or if I am using it wrong.

I've started using :
\consists "Mark_engraver"
\consists "Bar_number_engraver"
, etc
inside StaffGroups since it is now working.
(Fixed with I think 622cab6a34 (Thanks to Dan Eble))

But I get a strange and inconsistent result with whiteouts of the
Bar_number_engraver.
The two images I've attached to this email are from a 400+ measures
score. Sometimes the bar number is in front of the vertical system
line and sometimes it is behind. I have not figured out what is
different in each case as it pops-up rather anywhere.

But! I have managed (by error) to "trigger" the behavior in the
following MWE might you {un,}comment line 4.

\version "2.21.0"

music = \repeat unfold 7 {c'4}
%music = \repeat unfold 8 {c'4}

\score {
  <<
{s1 \break}
\new StaffGroup \music
\new StaffGroup \music
  >>
  \layout {
\override Score.BarNumber.self-alignment-X = #CENTER
\override Score.BarNumber.whiteout = #4
\context {
  \Score
  \remove "Bar_number_engraver"
}
\context {
  \StaffGroup
  \consists "Bar_number_engraver"
}
  }
}

Should a bug report be filed?

Thanks
-- 
Pierre-Luc Gauthier
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Spacing lyrics to avoid visible bar lines only

[joelhamme]

My fellow singers in choir have been asking me to improve the visual chunking
of choir staves. They wanted to have closed bar lines on the right edge of
each choir staff.

Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of clutter and
results in collisions with the lyrics, which is particularly unappealing
with thick repeat bars. This can be quickly fixed by adding `Bar_engraver`
to `Lyrics` and hiding them as described in ^[notation lyrics].

However, for aesthetical reasons I prefer removing all span bars, except
non-defaults and single bar bars at the end of each line. So this would
leave all repeats and double bar lines but no single bars unless there's a
line break, much like ^[semi choir staff snippet]

I've found a way to do this, except that there's some spacing issue with the
lyrics at single bars that aren't even shown. In choir staves, lyrics can
move below a bar line to take up the available space, which leaves a more
pleasing appearance and saves space on the page. Sadly, I could either make
the lyrics avoid all bar lines or not at all, but not only the ones that are
actually shown.

To the point:
I would like to make the lyrics avoid some span bars while not avoiding the
bar lines I've omitted using a call back.

To illustrate I've compiled a somewhat minimal example using long words to
trigger some collisions. For convenience I've also uploaded it to
^[lilybin].

 

```lilypond
\version "2.18.2"

link = {
  \once \override Score.RehearsalMark.self-alignment-X = #LEFT
  \mark \markup \normalsize {
\with-url #"http://lilybin.com/wmw4xx/6; "http://lilybin.com/wmw4xx/6;
  }
}

redspn = \once \override Score.SpanBar.color = #red
grnbar = \once \override Score.BarLine.color = #green

notes = {
  \link
  c1 \redspn | \repeat volta 2 { c | c \grnbar | c } | c | c | c \bar "|."
}

words = \lyricmode {
  Breathes | \markup { \with-color #red breathes } |
  br | \markup { \with-color #green breathes } |
  breathes | br | breathes |
}

\score {
  \new ChoirStaff <<
\new Staff \relative c'' \notes \addlyrics \words
\new Staff \relative c'' \notes
  >>

  \layout {
indent = 0
\context { \ChoirStaff
  \consists "Span_bar_engraver"
  \override BarLine.after-line-breaking =
#(lambda (grob)
  (if
(and (= 0 (ly:item-break-dir grob))
 (string=? (ly:grob-property grob 'glyph-name) "|") )
(ly:grob-set-property! grob 'allow-span-bar #f)))
}

% \context { \Lyrics
% \consists "Bar_engraver"
% \hide BarLine
% \override BarLine.after-line-breaking =
%   #(lambda (grob)
% (if
%   (and (= 0 (ly:item-break-dir grob)))
%(string=? (ly:grob-property grob 'glyph-name) "|")
%   (ly:grob-set-property! grob 'stencil #f))
%   )
% }
  }
}
```

The red colour indicates an unacceptable collision, whereas the green colour
indicates the desired loose spacing under bars that are not spanned across
staves. The commented-out section removes the relevant bar line stencils
from the lyrics, but fails to loosen the spacing where there are no longer
any bars to avoid.

Can I conditionally add bar lines to lyrics without otherwise affecting
their spacing?

Sorry this got so long, any help would be much appreciated.

Cheers,
Joel

[notation lyrics]:
http://lilypond.org/doc/v2.19/Documentation/notation/techniques-specific-to-lyrics#placing-syllables-horizontally
[semi choir staff snippet]: http://lsr.di.unimi.it/LSR/Item?id=299
[lilybin]: http://lilybin.com/wmw4xx/6




--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Spacing lyrics to avoid visible bar lines only

[Joel]

My fellow singers in choir have been asking me to improve the visual chunking 
of choir staves. They wanted to have closed bar lines on the right edge of each 
choir staff.

Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of clutter and 
results in collisions with the lyrics, which is particularly unappealing with 
thick repeat bars. This can be quickly fixed by adding `Bar_engraver` to 
`Lyrics` and hiding them as described in ^[notation lyrics].

However, for aesthetical reasons I prefer removing all span bars, except 
non-defaults and single bar bars at the end of each line. So this would leave 
all repeats and double bar lines but no single bars unless there's a line 
break, much like ^[semi choir staff snippet]

I've found a way to do this, except that there's some spacing issue with the 
lyrics at single bars that aren't even shown. In choir staves, lyrics can move 
below a bar line to take up the available space, which leaves a more pleasing 
appearance and saves space on the page. Sadly, I could either make the lyrics 
avoid all bar lines or not at all, but not only the ones that are actually 
shown.

To the point:
I would like to make the lyrics avoid some span bars while not avoiding the bar 
lines I've omitted using a call back.

To illustrate I've compiled a somewhat minimal example using long words to 
trigger some collisions. For convenience I've also uploaded it to ^[lilybin].



```lilypond
\version "2.18.2"

link = {
  \once \override Score.RehearsalMark.self-alignment-X = #LEFT
  \mark \markup \normalsize {
  \with-url #"http://lilybin.com/wmw4xx/6; "http://lilybin.com/wmw4xx/6;
  }
}

redspn = \once \override Score.SpanBar.color = #red
grnbar = \once \override Score.BarLine.color = #green

notes = {
  \link
  c1 \redspn | \repeat volta 2 { c | c \grnbar | c } | c | c | c \bar "|."
}

words = \lyricmode {
  Breathes | \markup { \with-color #red breathes } |
  br | \markup { \with-color #green breathes } |
  breathes | br | breathes |
}

\score {
  \new ChoirStaff <<
    \new Staff \relative c'' \notes \addlyrics \words
    \new Staff \relative c'' \notes
  >>

  \layout {
    indent = 0
    \context { \ChoirStaff
      \consists "Span_bar_engraver"
      \override BarLine.after-line-breaking =
        #(lambda (grob)
          (if
            (and (= 0 (ly:item-break-dir grob))
                 (string=? (ly:grob-property grob 'glyph-name) "|") )
            (ly:grob-set-property! grob 'allow-span-bar #f)))
    }

        % \context { \Lyrics
    % \consists "Bar_engraver"
    % \hide BarLine
    % \override BarLine.after-line-breaking =
    %   #(lambda (grob)
    %     (if
    %       (and (= 0 (ly:item-break-dir grob)))
    %            (string=? (ly:grob-property grob 'glyph-name) "|")
    %       (ly:grob-set-property! grob 'stencil #f))
    %   )
    % }
  }
}
```

The red colour indicates an unacceptable collision, whereas the green colour 
indicates the desired loose spacing under bars that are not spanned across 
staves. The commented-out section removes the relevant bar line stencils from 
the lyrics, but fails to loosen the spacing where there are no longer any bars 
to avoid.

Can I conditionally add bar lines to lyrics without otherwise affecting their 
spacing?

Sorry this got so long, any help would be much appreciated.

Cheers,
Joel

[notation lyrics]: 
http://lilypond.org/doc/v2.19/Documentation/notation/techniques-specific-to-lyrics#placing-syllables-horizontally
[semi choir staff snippet]: http://lsr.di.unimi.it/LSR/Item?id=299
[lilybin]: http://lilybin.com/wmw4xx/6
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Spacing lyrics to avoid visible bar lines only

[joelhamme]

My fellow singers in choir have been asking me to improve the visual chunking
of choir staves. They wanted to have closed bar lines on the right edge of
each choir staff.

Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of clutter and
results in collisions with the lyrics, which is particularly unappealing
with thick repeat bars. This can be quickly fixed by adding `Bar_engraver`
to `Lyrics` and hiding them as described in ^[notation lyrics].

However, for aesthetical reasons I prefer removing all span bars, except
non-defaults and single bar bars at the end of each line. So this would
leave all repeats and double bar lines but no single bars unless there's a
line break, much like ^[semi choir staff snippet]

I've found a way to do this, except that there's some spacing issue with the
lyrics at single bars that aren't even shown. In choir staves, lyrics can
move below a bar line to take up the available space, which leaves a more
pleasing appearance and saves space on the page. Sadly, I could either make
the lyrics avoid all bar lines or not at all, but not only the ones that are
actually shown.

To the point:
I would like to make the lyrics avoid some span bars while not avoiding the
bar lines I've omitted using a call back.

To illustrate I've compiled a somewhat minimal example using long words to
trigger some collisions. For convenience I've also uploaded it to
^[lilybin].

 

```lilypond
\version "2.18.2"

link = {
  \once \override Score.RehearsalMark.self-alignment-X = #LEFT
  \mark \markup \normalsize {
\with-url #"http://lilybin.com/wmw4xx/6; "http://lilybin.com/wmw4xx/6;
  }
}

redspn = \once \override Score.SpanBar.color = #red
grnbar = \once \override Score.BarLine.color = #green

notes = {
  \link
  c1 \redspn | \repeat volta 2 { c | c \grnbar | c } | c | c | c \bar "|."
}

words = \lyricmode {
  Breathes | \markup { \with-color #red breathes } |
  br | \markup { \with-color #green breathes } |
  breathes | br | breathes |
}

\score {
  \new ChoirStaff <<
\new Staff \relative c'' \notes \addlyrics \words
\new Staff \relative c'' \notes
  >>

  \layout {
indent = 0
\context { \ChoirStaff
  \consists "Span_bar_engraver"
  \override BarLine.after-line-breaking =
#(lambda (grob)
  (if
(and (= 0 (ly:item-break-dir grob))
 (string=? (ly:grob-property grob 'glyph-name) "|") )
(ly:grob-set-property! grob 'allow-span-bar #f)))
}

% \context { \Lyrics
% \consists "Bar_engraver"
% \hide BarLine
% \override BarLine.after-line-breaking =
%   #(lambda (grob)
% (if
%   (and (= 0 (ly:item-break-dir grob)))
%(string=? (ly:grob-property grob 'glyph-name) "|")
%   (ly:grob-set-property! grob 'stencil #f))
%   )
% }
  }
}
```

The red colour indicates an unacceptable collision, whereas the green colour
indicates the desired loose spacing under bars that are not spanned across
staves. The commented-out section removes the relevant bar line stencils
from the lyrics, but fails to loosen the spacing where there are no longer
any bars to avoid.

Can I conditionally add bar lines to lyrics without otherwise affecting
their spacing?

Sorry this got so long, any help would be much appreciated.

Cheers,
Joel

[notation lyrics]:
http://lilypond.org/doc/v2.19/Documentation/notation/techniques-specific-to-lyrics#placing-syllables-horizontally
[semi choir staff snippet]: http://lsr.di.unimi.it/LSR/Item?id=299
[lilybin]: http://lilybin.com/wmw4xx/6




--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Spacing lyrics to avoid visible bar lines only

[joelhamme]

My fellow singers in choir have been asking me to improve the visual chunking
of choir staves. They wanted to have closed bar lines on the right edge of
each choir staff.

Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of clutter and
results in collisions with the lyrics, which is particularly unappealing
with thick repeat bars. This can be quickly fixed by adding `Bar_engraver`
to `Lyrics` and hiding them as described in ^[notation lyrics].

However, for aesthetical reasons I prefer removing all span bars, except
non-defaults and single bar bars at the end of each line. So this would
leave all repeats and double bar lines but no single bars unless there's a
line break, much like ^[semi choir staff snippet]

I've found a way to do this, except that there's some spacing issue with the
lyrics at single bars that aren't even shown. In choir staves, lyrics can
move below a bar line to take up the available space, which leaves a more
pleasing appearance and saves space on the page. Sadly, I could either make
the lyrics avoid all bar lines or not at all, but not only the ones that are
actually shown.

To the point:
I would like to make the lyrics avoid some span bars while not avoiding the
bar lines I've omitted using a call back.

To illustrate I've compiled a somewhat minimal example using long words to
trigger some collisions. For convenience I've also uploaded it to
^[lilybin].

 

```lilypond
\version "2.18.2"

link = {
  \once \override Score.RehearsalMark.self-alignment-X = #LEFT
  \mark \markup \normalsize {
\with-url #"http://lilybin.com/wmw4xx/6; "http://lilybin.com/wmw4xx/6;
  }
}

redspn = \once \override Score.SpanBar.color = #red
grnbar = \once \override Score.BarLine.color = #green

notes = {
  \link
  c1 \redspn | \repeat volta 2 { c | c \grnbar | c } | c | c | c \bar "|."
}

words = \lyricmode {
  Breathes | \markup { \with-color #red breathes } |
  br | \markup { \with-color #green breathes } |
  breathes | br | breathes |
}

\score {
  \new ChoirStaff <<
\new Staff \relative c'' \notes \addlyrics \words
\new Staff \relative c'' \notes
  >>

  \layout {
indent = 0
\context { \ChoirStaff
  \consists "Span_bar_engraver"
  \override BarLine.after-line-breaking =
#(lambda (grob)
  (if
(and (= 0 (ly:item-break-dir grob))
 (string=? (ly:grob-property grob 'glyph-name) "|") )
(ly:grob-set-property! grob 'allow-span-bar #f)))
}

% \context { \Lyrics
% \consists "Bar_engraver"
% \hide BarLine
% \override BarLine.after-line-breaking =
%   #(lambda (grob)
% (if
%   (and (= 0 (ly:item-break-dir grob)))
%(string=? (ly:grob-property grob 'glyph-name) "|")
%   (ly:grob-set-property! grob 'stencil #f))
%   )
% }
  }
}
```

The red colour indicates an unacceptable collision, whereas the green colour
indicates the desired loose spacing under bars that are not spanned across
staves. The commented-out section removes the relevant bar line stencils
from the lyrics, but fails to loosen the spacing where there are no longer
any bars to avoid.

Can I conditionally add bar lines to lyrics without otherwise affecting
their spacing?

Sorry this got so long, any help would be much appreciated.

Cheers,
Joel

[notation lyrics]:
http://lilypond.org/doc/v2.19/Documentation/notation/techniques-specific-to-lyrics#placing-syllables-horizontally
[semi choir staff snippet]: http://lsr.di.unimi.it/LSR/Item?id=299
[lilybin]: http://lilybin.com/wmw4xx/6




--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: chord duration

[Torsten Hämmerle]

Gianmaria Lari wrote
> Ciao Torsten,
> 
> I'm sorry, I don't understand. Why I would like to display twice a chord
> if
> I write c4~4 ? Maybe could you write a simple example (if possible!).

Ah, yes, right, Gianmaria!

I only was thinking of chord changes in general, but now I see that it's
primarily about the tie.
And, I agree, there is no reason why one would want to display a tied-over
chord name.
Except, perhaps after line breaks (cf. accidentals). 

All the best,
Torsten




--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Omitting specific symbols from key signatures

[Adam Good]

On Wed, Oct 31, 2018 at 10:48 AM Torsten Hämmerle 
wrote:

> Yes, I'm on the dev list.
> And I'll appreciate a co-operation regarding makam issues.
> After all, you and Hans can provide valuable practical examples, and one
> important point after finally having added my new accidental glyphs, all
> the
> non-standard accidental combinations in key signatures music currently
> suffer from several spacing problems, because currently, for obvious
> reasons, the focus had been solely on standard western accidentals.


Excellent let's bring it over there! I'll come up with a couple basic
examples. And my apologies for not immediately recognizing your name from
the thread RE: glyphs.

Thank you for all of this!

Adam
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: chord duration

[Gianmaria Lari]

On Wed, 31 Oct 2018 at 15:45, Torsten Hämmerle 
wrote:

> Gianmaria Lari wrote
> > But I was wondering why it should not work my
> > obvious solution :)
>
> Ciao Gianmanria,
>
> Probably because your obvious solution isn't that obvious from a technical
> point of view.
> In this simple example, it is totally clear that we only want to see
> changes.
> But just imagine the beginning of a new section (rehearsal mark, repeat
> volta bracket, Coda, etc.) where we definitely *want* to clearly re-instate
> the Chord name for several reasons.
>
> I think it is necessary to deliberately set chordChanges to ##t or ##f in
> many cases.
>
> Besides, I'll opt for ##t as the default setting.


Ciao Torsten,

I'm sorry, I don't understand. Why I would like to display twice a chord if
I write c4~4 ? Maybe could you write a simple example (if possible!).

Thank you Torsten!
g.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Omitting specific symbols from key signatures

[Torsten Hämmerle]

Adam Good-3 wrote
> Are you on the dev list? If you'd be willing to help me out some more I
> can
> send you a couple of files that are under development and we can address
> specifically the two makams that have this issue.


Yes, I'm on the dev list.
And I'll appreciate a co-operation regarding makam issues.
After all, you and Hans can provide valuable practical examples, and one
important point after finally having added my new accidental glyphs, all the
non-standard accidental combinations in key signatures music currently
suffer from several spacing problems, because currently, for obvious
reasons, the focus had been solely on standard western accidentals.

All the best,
Torsten




--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: chord duration

[Torsten Hämmerle]

Gianmaria Lari wrote
> But I was wondering why it should not work my
> obvious solution :)

Ciao Gianmanria,

Probably because your obvious solution isn't that obvious from a technical
point of view.
In this simple example, it is totally clear that we only want to see
changes.
But just imagine the beginning of a new section (rehearsal mark, repeat
volta bracket, Coda, etc.) where we definitely *want* to clearly re-instate
the Chord name for several reasons.

I think it is necessary to deliberately set chordChanges to ##t or ##f in
many cases.

Besides, I'll opt for ##t as the default setting.

All the best,
Torsten



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Omitting specific symbols from key signatures

[Adam Good]

Torsten that's GREAT! Very very nice and works so well. But it's working a
little too well for my purposes :)

Are you on the dev list? If you'd be willing to help me out some more I can
send you a couple of files that are under development and we can address
specifically the two makams that have this issue.

Let me know and thanks ahead!!

Adam

On Wed, Oct 31, 2018 at 9:08 AM Torsten Hämmerle 
wrote:

> Adam Good-3 wrote
> > Thank you Torsten, unfortunately this doesn't satisfy the criteria of #3
> > request, working across transpositions. If I ask for:
> > \key c \KeySig
> >
> > ...it prints a ces in the key signature. […]
>
> Hi Adam,
>
> Yes, unfortunately, my trickery only works for keys with a "sharp" tonic.
> In
> other cases, e.g. starting with a C, the artificially lowered first step in
> the scale will get a flat in the key signature, which is not what you asked
> for…
>
>
> The consequence of all this simply is that we need a *flexible* key
> signature dynamically reacting on the current tonic:
> If the tonic does not take any accidental (as in your C example), do
> nothing.
> If, however, the tonic has an accidental (no matter if it's a sharp, a
> flat,
> a semi-sharp or whatever) just leave it away.
>
> So, we can't get away with just specifying a fixed, well defined key
> signature, but we have to look for the current tonic and, if there's an
> accidental in the key sig, remove it.
>
> Unfortunately, the grob does not know the tonic and we have to read it from
> the context.
> To make it even worse, everything may change if we apply transposition.
>
> So, based on the naturalize-pitch snipped, I've defined a \makamKey
> function
> that reads all the music and eventually kicks out tonic accidentals from
> the
> key signature (i.e. pitch-alist).
> That way, a fis or bes tonic will never be displayed in the key signature
> but will be printed each time as an individual accidental.
> But a c tonic, for instance, will have no influence on the key signature
> (i.e. no superfluous unwanted accidentals).
>
> %%%
> \version "2.18.2"
>
> #(define (makam-alist tonic alist)
>(let ((tonic-step (ly:pitch-notename tonic))
>  (tonic-alt (ly:pitch-alteration tonic)))
>  (if (eqv? tonic-alt 0)
>  alist
>  (filter (lambda (s) (not (eqv? tonic-step (car s
>  alist
>
> #(define (makam-key music)
>(let ((es (ly:music-property music 'elements))
>  (e (ly:music-property music 'element))
>  (tonic (ly:music-property music 'tonic))
>  (pitch-alist (ly:music-property music 'pitch-alist)))
>  (if (pair? es)
>  (ly:music-set-property!
>   music 'elements
>   (map makam-key es)))
>  (if (ly:music? e)
>  (ly:music-set-property!
>   music 'element
>   (makam-key e)))
>  (if (pair? pitch-alist)
>  (ly:music-set-property!
>   music 'pitch-alist (makam-alist tonic pitch-alist)))
>  music))
>
> makamKey =
> #(define-music-function (parser location m)
>(ly:music?)
>(makam-key m))
>
> testmusic = \makamKey \relative c' {
>   \key fis \locrian fis4 g a b c d e fis
> }
>
> { \testmusic }
> \transpose fis c \testmusic
> \transpose fis dis \testmusic
> \transpose fis bes, \testmusic
> 
>
> 
>
>
> HTH,
> Torsten
>
> a
>
>
>
> --
> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Omitting specific symbols from key signatures

[Torsten Hämmerle]

Adam Good-3 wrote
> Thank you Torsten, unfortunately this doesn't satisfy the criteria of #3
> request, working across transpositions. If I ask for:
> \key c \KeySig
> 
> ...it prints a ces in the key signature. […]

Hi Adam,

Yes, unfortunately, my trickery only works for keys with a "sharp" tonic. In
other cases, e.g. starting with a C, the artificially lowered first step in
the scale will get a flat in the key signature, which is not what you asked
for…


The consequence of all this simply is that we need a *flexible* key
signature dynamically reacting on the current tonic:
If the tonic does not take any accidental (as in your C example), do
nothing.
If, however, the tonic has an accidental (no matter if it's a sharp, a flat,
a semi-sharp or whatever) just leave it away.

So, we can't get away with just specifying a fixed, well defined key
signature, but we have to look for the current tonic and, if there's an
accidental in the key sig, remove it.

Unfortunately, the grob does not know the tonic and we have to read it from
the context.
To make it even worse, everything may change if we apply transposition.

So, based on the naturalize-pitch snipped, I've defined a \makamKey function
that reads all the music and eventually kicks out tonic accidentals from the
key signature (i.e. pitch-alist).
That way, a fis or bes tonic will never be displayed in the key signature
but will be printed each time as an individual accidental.
But a c tonic, for instance, will have no influence on the key signature
(i.e. no superfluous unwanted accidentals).

%%%
\version "2.18.2"

#(define (makam-alist tonic alist)
   (let ((tonic-step (ly:pitch-notename tonic))
 (tonic-alt (ly:pitch-alteration tonic)))
 (if (eqv? tonic-alt 0)
 alist
 (filter (lambda (s) (not (eqv? tonic-step (car s
 alist

#(define (makam-key music)
   (let ((es (ly:music-property music 'elements))
 (e (ly:music-property music 'element))
 (tonic (ly:music-property music 'tonic))
 (pitch-alist (ly:music-property music 'pitch-alist)))
 (if (pair? es)
 (ly:music-set-property!
  music 'elements
  (map makam-key es)))
 (if (ly:music? e)
 (ly:music-set-property!
  music 'element
  (makam-key e)))
 (if (pair? pitch-alist)
 (ly:music-set-property!
  music 'pitch-alist (makam-alist tonic pitch-alist)))
 music))

makamKey =
#(define-music-function (parser location m)
   (ly:music?)
   (makam-key m))

testmusic = \makamKey \relative c' {
  \key fis \locrian fis4 g a b c d e fis
}

{ \testmusic }
\transpose fis c \testmusic
\transpose fis dis \testmusic
\transpose fis bes, \testmusic


 

HTH,
Torsten

a



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Werner LEMBERG]

> I don't regard this as done and dusted yet.

Thanks!

> It fails on a Mac pristine install for High Sierra. This is not good
> at all. I'm am continuing to look further into this very pinpoint
> specific failure pattern. It's odd.

What about trying the MacPorts version?  The package is called
`lilypond-devel' and provides 2.19.80.  This should deliver the newest
versions of all libraries.


Werner

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: UTF-8-aware backwards string searching in Guile, or: fixing centered lyrics ignoring punctuation

[Alexander Kobel]

Gosh,

once again I'm flabbergasted about the expertise and helpfulness of the 
folks on this list. Thanks a ton!


As far as I can tell, your corrected version works like a charm (and 
even fixed a minor misalignment of the "à" syllable that I did not spot 
earlier). And IIUC, the only drawback of the quick'n'dirty variant is 
that it does not actually do a canonicalization of the strings involved, 
so that two different representations of a glyph (e.g., using different 
combining characters) will not match. But this is extremely unlikely 
given that they should be usually entered by the same user in the same 
way, and that the set of characters to compare with is fairly limited 
and probably even has a unique encoding anyway.

So, problem solved for me.

I can only hope that you did not spend the 4.75 hours between your mails 
for the "quick fix"...



Cheers,
Alex


On 31/10/2018 05.23, Aaron Hill wrote:

On 2018-10-30 4:56 pm, Aaron Hill wrote:

On 2018-10-30 10:01 am, Alexander Kobel wrote:

Does anyone have a hint how to approach this one? (Or is the answer
just: be patient and hope for Guile v2?)


The only hint here is to replace the built-in functions with ones
which understand UTF8 encoding and can perform the work needed.  There
very well might be someone online who has already done this work,
which would save on having to do it yourself.

Otherwise, the basic strategy is to replace string->list with a
version that decodes UTF8 and returns a list of integers (essentially
UTF32).  Then, all of the string work is being done with these lists
of integers instead.  (The character set would also just be a set of
integers representing the unique Unicode code points.)  After you find
the subsets of the list that are interesting to measure, you'll then
need to convert the list back into a string.  This means encoding back
into UTF8 and emitting a string.


Here's a quick-n-dirty patch to address the issue.


\version "2.19.82"
\include "center-lyrics-ignoring-punctuation.ily"
{ d'4 4 4 }
\addlyrics { Å Ɓ† «Ḉ…» }


-- Aaron Hill

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user





smime.p7s
Description: S/MIME Cryptographic Signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Aaron Hill]

On 2018-10-31 1:59 am, Andrew Bernard wrote:

Hi All,

It's something much more subtle than the system/user font location. On 
my
system, despite Kieran's success, it does not work, and when K upgrades 
the
mac it may not work for him. In correspondence with the typographer of 
the

font, we have all definitively established what the correct version is.

This matter is specific to Alegreya, to the Mac, and to lilypond using 
it,
not other programs. It does not arise with any other font that I know 
(but
it is hard to test hundreds of thousands...) and does not arise on 
Windows

or various Linux distros.

I don't regard this as done and dusted yet. It fails on a Mac pristine
install for High Sierra. This is not good at all. I'm am continuing to 
look

further into this very pinpoint specific failure pattern. It's odd.


Hi Andrew,

I don't have access to any Mac environments, or else I'd help you chase 
this down.  But I did have a few ideas for next steps, assuming you have 
not already done them.


The GitHub for the foundry has older versions of the font family as well 
as other fonts they publish.  In the event there is something in their 
workflow that generates fonts with a rare but buggy characteristic, it 
would be good to test as many fonts there as reasonable.  Especially it 
would be good to test older versions of the fonts that known to fail.  
If the failing case is exclusive to one or more specific versions, that 
might help to track down the underlying issue.


-- Aaron Hill

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Andrew Bernard]

Hi All,

It's something much more subtle than the system/user font location. On my
system, despite Kieran's success, it does not work, and when K upgrades the
mac it may not work for him. In correspondence with the typographer of the
font, we have all definitively established what the correct version is.

This matter is specific to Alegreya, to the Mac, and to lilypond using it,
not other programs. It does not arise with any other font that I know (but
it is hard to test hundreds of thousands...) and does not arise on Windows
or various Linux distros.

I don't regard this as done and dusted yet. It fails on a Mac pristine
install for High Sierra. This is not good at all. I'm am continuing to look
further into this very pinpoint specific failure pattern. It's odd.

Andrew



On Wed, 31 Oct 2018 at 11:57, Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:

> Hi,
>
> > If the problem is Mac related, then it might have to do with System
> fonts (located in /Library/Fonts) vs. User fonts (located in
> Users//Library/Fonts).  IIRC, the default installation location
> when using Font Book is the User location.
>
> Good thought… but in my case, I know for sure that all fonts were
> installed at the Computer/System level. It was definitely the source (and
> therefore, likely, the version) of the font that determined success or
> failure.
>
> Cheers,
> Kieren.
> 
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: chord duration

[Gianmaria Lari]

On Wed, 31 Oct 2018 at 09:21, David Kastrup  wrote:

> Gianmaria Lari  writes:
>
> > The following code...
> >
> > \version "2.19.82"
> > \new ChordNames \chordmode { c8~c2 }
> >
> >
> > displays C C. How can I make it display a single C chord that last 8~2?
>
> You got a number of workarounds in different answers.  There may also be
> some point in treating this as a bug.


:)

The three solution  Schmaus, Meyn, Moser, Hill (and Barker) proposed work
well (thank you all of you!). But I was wondering why it should not work my
obvious solution :)

Thank you David!
Best regards, g.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: chord duration

[David Kastrup]

Gianmaria Lari  writes:

> The following code...
>
> \version "2.19.82"
> \new ChordNames \chordmode { c8~c2 }
>
>
> displays C C. How can I make it display a single C chord that last 8~2?

You got a number of workarounds in different answers.  There may also be
some point in treating this as a bug.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: chord duration

[Lukas-Fabian Moser]

Am 31.10.18 um 09:00 schrieb Gianmaria Lari:

The following code...

\version "2.19.82"
\new ChordNames \chordmode { c8~c2 }


displays C C. How can I make it display a single C chord that last 8~2?


Durations may be modified using factors: since 2 is 4x 8 (hehe), you can 
write \chordmode { c8*5 }.


(Alternatively, replace the second chord by a skip: s2)

Lukas


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: chord duration

[Aaron Hill]

On 2018-10-31 1:00 am, Gianmaria Lari wrote:

The following code...

\version "2.19.82"
\new ChordNames \chordmode { c8~c2 }


displays C C. How can I make it display a single C chord that last 8~2?


Would either "c8 s2" or "c8*5" work for you?  (I think the second one 
would be needed for MIDI output to work correctly.)


-- Aaron Hill

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: chord duration

[Malte Meyn]

Am 31.10.18 um 09:00 schrieb Gianmaria Lari:

The following code...

\version "2.19.82"
\new ChordNames \chordmode { c8~c2 }


displays C C. How can I make it display a single C chord that last 8~2?


There are several possibilities:

%%%
\version "2.19.82"

\new ChordNames \with {
  chordChanges = ##t % don’t repeat unchanged chord
} \chordmode { c8 c2 }

\new ChordNames \chordmode { c8 s2 } % set a spacer rest instead of c2

\new ChordNames \chordmode { c8*5 } % chord with duration 8*5 = 8~2
%%%

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: chord duration

[Robert Schmaus]

Try C8*5. 

Best,
Robert

> On 31 Oct 2018, at 09:00, Gianmaria Lari  wrote:
> 
> The following code... 
> 
> \version "2.19.82"
> \new ChordNames \chordmode { c8~c2 }
> 
> displays C C. How can I make it display a single C chord that last 8~2?
> 
> Thank you, g.
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

chord duration

[Gianmaria Lari]

The following code...

\version "2.19.82"
\new ChordNames \chordmode { c8~c2 }


displays C C. How can I make it display a single C chord that last 8~2?

Thank you, g.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: \RemoveEmptyStaves not removing first line

[Lukas-Fabian Moser]

(Replying to list, assuming you wrote to me personally only by accident, 
as implied by your wording):


Am 31.10.18 um 00:42 schrieb Rohan Srinivasan:
Could any of you give me an example of how \RemoveAllEmptyStaves is 
used? I have:


\layout {
  \context {
    \Staff
    \RemoveAllEmptyStaves
  }
}

This still doesn't seem to clear the empty staves in the first system.


Please always try to provide a compilable minimal example showing your 
problem.


\version "2.19.80"

\layout {
  \context {
    \Staff
    \RemoveAllEmptyStaves
  }
}

<<
  \new Staff \with { instrumentName = "Voice" shortInstrumentName = 
"Voc" } { R1*30 \repeat unfold 80 c'4 }
  \new PianoStaff \with { instrumentName = "Piano" shortInstrumentName 
= "Pn" } <<

    \new Staff { \repeat unfold 200 c'4 }
    \new Staff { \clef bass \repeat unfold 400 c8 }
  >>
>>

works here:

Best
Lukas

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond-invoke-editor in Windows

[Aaron Hill]

On 2018-10-31 12:34 am, David Kastrup wrote:

Federico Bruni  writes:


Hi all

I'm trying again to make lilypond-invoke-editor work in Windows.
Someone managed to make it work using Windows Subsystem for Linux,
that is installing the LylyPond Linux binary in Windows. But I'd like
to use the installation for Windows.

I think I'm really close to it.
The easiest setup seems to add all the necessary environment variables
and add LilyPond bin/ directory to the path.
Now I'm at a point where in Git Bash I can easily run
lilypond-invoke-editor without errors.
Except when I try to open a URI and the $(file)s, $(line)s and
$(column)s variables are not expanded. What do you think it's missing?
It may be a bug in editor.scm?

$ echo $LYEDITOR
"C:\Program Files\Microsoft VS Code\bin\code" --goto
$(file)s:$(line)s:$(column)s

$ lilypond-invoke-editor
textedit:///c/Users/test/Documents/test.ly:1:1:1
Arguments in `--goto` mode should be in the format of
`FILE(:LINE(:CHARACTER))`.
lilypond-invoke-editor (GNU LilyPond) 2.19.82


You have one :1 too many.


Technically, the format is file:line:char:column, so you can have three 
values.  Granted, I've never quite understood the distinction between 
"char" and "column".  Usually column is one more than char, so perhaps 
it's a count-from-zero vs. count-from-one thing.  *shrug*


But I think the original issue is the use of $(file)s instead of 
%(file)s.  editor.scm expects a percent sign if I am reading the code 
correctly.


-- Aaron Hill

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond-invoke-editor in Windows

[David Kastrup]

Federico Bruni  writes:

> Hi all
>
> I'm trying again to make lilypond-invoke-editor work in Windows.
> Someone managed to make it work using Windows Subsystem for Linux,
> that is installing the LylyPond Linux binary in Windows. But I'd like
> to use the installation for Windows.
>
> I think I'm really close to it.
> The easiest setup seems to add all the necessary environment variables
> and add LilyPond bin/ directory to the path.
> Now I'm at a point where in Git Bash I can easily run
> lilypond-invoke-editor without errors.
> Except when I try to open a URI and the $(file)s, $(line)s and
> $(column)s variables are not expanded. What do you think it's missing?
> It may be a bug in editor.scm?
>
> $ echo $LYEDITOR
> "C:\Program Files\Microsoft VS Code\bin\code" --goto
> $(file)s:$(line)s:$(column)s
>
> $ lilypond-invoke-editor
> textedit:///c/Users/test/Documents/test.ly:1:1:1
> Arguments in `--goto` mode should be in the format of
> `FILE(:LINE(:CHARACTER))`.
> lilypond-invoke-editor (GNU LilyPond) 2.19.82

You have one :1 too many.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

lilypond-invoke-editor in Windows

[Federico Bruni]

Hi all

I'm trying again to make lilypond-invoke-editor work in Windows.
Someone managed to make it work using Windows Subsystem for Linux, that 
is installing the LylyPond Linux binary in Windows. But I'd like to use 
the installation for Windows.


I think I'm really close to it.
The easiest setup seems to add all the necessary environment variables 
and add LilyPond bin/ directory to the path.
Now I'm at a point where in Git Bash I can easily run 
lilypond-invoke-editor without errors.
Except when I try to open a URI and the $(file)s, $(line)s and 
$(column)s variables are not expanded. What do you think it's missing? 
It may be a bug in editor.scm?


$ echo $LYEDITOR
"C:\Program Files\Microsoft VS Code\bin\code" --goto 
$(file)s:$(line)s:$(column)s


$ lilypond-invoke-editor 
textedit:///c/Users/test/Documents/test.ly:1:1:1
Arguments in `--goto` mode should be in the format of 
`FILE(:LINE(:CHARACTER))`.

lilypond-invoke-editor (GNU LilyPond) 2.19.82

# dummy test to show that the editor (VS Code) command is failing
$ code --goto Documents/test.ly:file:line:column
Arguments in `--goto` mode should be in the format of 
`FILE(:LINE(:CHARACTER))`.






___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user