Re: Old completion engraver bug

2020-08-17 Thread Jon Arnold
Yes, this works well! Thanks very much.

On Sat, Aug 15, 2020 at 3:10 PM Thomas Morley 
wrote:

> Am Sa., 15. Aug. 2020 um 18:49 Uhr schrieb Jon Arnold
> :
> >
> > Hi all-
> >
> > I'm working on 14 pieces for my dissertation that use the completion
> > engravers heavily. I've just noticed a problem with lyrics alignment,
> which
> > is documented in this old bug:
> > https://sourceforge.net/p/testlilyissues/issues/1928/
> >
> > Is there any more current work around or hope of getting this fixed? It
> > shows up all over my pieces, and I am really hoping not to have to fix it
> > manually.
> >
> > Thanks!
> >
> > Jon Arnold
> > ___
> > bug-lilypond mailing list
> > bug-lilypond@gnu.org
> > https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
> Hi,
>
> probably below.
> Please report back if it's a sufficient workaround worth adding to the
> issue
>
>
> #(define lyric-text-at-splitted-notes
> ;; Left-align LyricText if the NoteHead is splitted by
> Completion_heads_engraver
>   (lambda (grob)
> (let* (;; x-parent is usually NoteColumn
>(x-parent (ly:grob-parent grob X))
>;; NoteHeads (as array)
>(x-parent-nhds-array (ly:grob-object x-parent 'note-heads))
>;; NoteHeads (as list or #f)
>(x-parent-nhds
>  (if (ly:grob-array? x-parent-nhds-array)
>  (ly:grob-array->list x-parent-nhds-array)
>  #f)))
>   ;; If NoteHeads are splitted by Completion_heads_engraver, the
>   ;; 'autosplit-end prob-property is true
>   (if x-parent-nhds
>   (for-each
> (lambda (nhd)
>   (let* ((cause (ly:grob-property nhd 'cause))
>  (splitted? (ly:prob-property cause 'autosplit-end
> #f)))
> (if splitted?
> (ly:grob-set-property! grob 'self-alignment-X LEFT
> x-parent-nhds)
>
> \layout {
>   \context {
>   \Lyrics
>   \override LyricText.before-line-breaking =
> #lyric-text-at-splitted-notes
>   }
> }
>
> mel = \relative c'' {
>   c2 d1 c1 c2
> }
>
> lyr = \lyricmode {
>   One -- two __ three -- four.
> }
>
> \score {
>   <<
> \new Staff \new Voice = "normal" \mel
> \new Lyrics \lyricsto "normal" \lyr
>
> \new Staff <<
>   \new Voice = "completion"
> \with {
>   \remove "Note_heads_engraver"
>   \consists "Completion_heads_engraver"
> }
>   \mel
> >>
> \new Lyrics \lyricsto "completion" \lyr
>
> \new Staff \new Voice = "revisited" \relative c'' { c2 c~ c c~ c c }
> \new Lyrics \lyricsto "revisited" \lyr
>   >>
> }
>
> Cheers,
>   Harm
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Old completion engraver bug

2020-08-15 Thread Jon Arnold
Hi all-

I'm working on 14 pieces for my dissertation that use the completion
engravers heavily. I've just noticed a problem with lyrics alignment, which
is documented in this old bug:
https://sourceforge.net/p/testlilyissues/issues/1928/

Is there any more current work around or hope of getting this fixed? It
shows up all over my pieces, and I am really hoping not to have to fix it
manually.

Thanks!

Jon Arnold
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Problems with horizontal brackets

2020-05-30 Thread Jon Arnold
Hi-
I'm using horizontal brackets to analyze a piece that makes heavy use of
the completion engravers, and I've discovered that the brackets do not
extend the full length of a note when tied over a bar. The bracket only
goes as far as the beginning of the expanded value.

Perhaps the last bit should be filed separately, but the brackets do not
appear at all when using full measure rests.

Here's my example:

%horizontal brackets do not extend the full length of the note
%if used on a note expanded by completion engravers

%they also do not appear at all on full measure rests

\version "2.21.1"

\score {
  \new Staff {
a1-\startGroup c'\breve-\stopGroup  \break
r1-\startGroup r\breve-\stopGroup \break
R1-\startGroup R\breve-\stopGroup
  }
  \layout {
\context {
  \Voice
  \remove "Note_heads_engraver"
  \consists "Completion_heads_engraver"
  \remove "Rest_engraver"
  \consists "Completion_rest_engraver"
  \consists "Horizontal_bracket_engraver"
}
  }
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Bug: parenthesize before line break

2017-04-11 Thread Jon Arnold
Trying again on this, and I've attached a PNG this time.

On Tue, Apr 4, 2017 at 2:59 PM, Jon Arnold <jonarnoldsem...@gmail.com>
wrote:

> When I try to parenthesize a breathe mark that is right before a line
> break, Lilypond engraves the parentheses on the next line to the left of
> the clef sign, rather than the line that it should be.
>
>
> %%% BUG REPORT START
> %parenthesize just before line break prints on next line
> \version "2.19.58"
>
> \relative c'' {
>   b4 c \parenthesize \breathe d f \parenthesize \breathe \break
>   e \parenthesize \breathe d c \parenthesize \breathe a
> }
>
> %%% BUG REPORT END
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Bug: parenthesize before line break

2017-04-04 Thread Jon Arnold
When I try to parenthesize a breathe mark that is right before a line
break, Lilypond engraves the parentheses on the next line to the left of
the clef sign, rather than the line that it should be.


%%% BUG REPORT START
%parenthesize just before line break prints on next line
\version "2.19.58"

\relative c'' {
  b4 c \parenthesize \breathe d f \parenthesize \breathe \break
  e \parenthesize \breathe d c \parenthesize \breathe a
}

%%% BUG REPORT END
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


DynamicTextSpanners should end like hairpins

2010-08-11 Thread Jon Arnold
 I'm not top posting.

DynamicTextSpanners in their current state will prevent hairpins from being 
produced properly if the space is small.

The DynamicTextSpanner should have the same right boundary as a hairpin (i.e. a 
\cresc should end at the same place as a \ ). They should also behave the same 
way at barlines.

The following example demonstrates the behavior of a \cresc and a crescendo 
hairpin at the same place. Notice that the following diminuendo hairpin is cut 
off in the first example. The final example shows the proper diminuendo 
hairpin, 
as the \cresc is ended a beat earlier than in the original music.

The second set of examples shows similar behavior but ending at a barline.

http://dl.dropbox.com/u/143104/dynamicSpannerIssue.ly
http://dl.dropbox.com/u/143104/dynamicSpannerIssue.png


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond