bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LSR for two opposing fermatas fails on staff change


From: Xavier Scheuer
Subject: Re: LSR for two opposing fermatas fails on staff change
Date: Sun, 10 Feb 2013 12:59:45 +0100

On 10 February 2013 09:43, Javier Ruiz-Alma <address@hidden> wrote:
> The LSR for typesetting two opposing fermatas above/below a barline will not
> produce desired result when voices converge on one staff.  Suggest adding a 
> note
> of this, or better yet, how one could overcome this.
>
> http://lsr.dsi.unimi.it/LSR/Item?id=10
>
> (snip)
>

I use Neil's "multi-mark-engraver"
http://lists.gnu.org/archive/html/lilypond-user/2011-08/msg00157.html
and so far I never encountered any side-effect.

%%%% Lily code

% you should include the definition of "multi-mark-engraver"
% http://lists.gnu.org/archive/html/lilypond-user/2011-08/msg00157.html

markDown =
#(define-music-function (parser location text) (markup?)
   (make-music 'MarkEvent
               'direction DOWN
               'label text))

\layout {
  \context {
    \Score
    \remove "Mark_engraver"
    \consists #multi-mark-engraver
    \consists "Tweak_engraver"
  }
}

soprano = {
  c''2 \change Staff = "lower" d''2
 \override Score.RehearsalMark #'break-visibility = #begin-of-line-invisible
 \mark \markup { \musicglyph #"scripts.ufermata" }
}
bass = {
  a'1
  \markDown \markup { \musicglyph #"scripts.dfermata" }
}
\score {
  \new GrandStaff <<
    \new Staff = "upper" { \soprano }
    \new Staff = "lower" { \bass }
  >>
  \layout {
  }
}

%%%% End of lily code

Cheers,
Xavier

PS: I do not think a limitation in a LSR snippet that is AFAIK not part
of LilyPond official documentation could qualify as a bug.
But adding "multi-mark-engraver" features in LilyPond by default could
(should?) be considered as a nice feature request.

-- 
Xavier Scheuer <address@hidden>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]