Re: Stacking lyrics above dynamics?

[Mats Bengtsson]

Your question is completely unrelated to Trevor's, since Lyrics are typeset
by a completely separate context (so his problem is equivalent to 
putting the
dynamics of of stave below the next stave, when it comes to how LilyPond
handles it). Your question is about different objects that are handled 
in the
same Staff (or even Voice) context. Since version 2.8, it is possible to 
specify
how LilyPond should avoid collisions between slurs and other objects, see
the example called slur-script-inside.ly in the Regression Test document.

  /Mats

Anthony Youngman wrote:
> Following up on that, is there any way of altering which way round other marks 
> go? I certainly haven't hit the lyrics/dynamics problems (apart from 
> Pennsylvania I haven't used lyrics :-), but the problem I have is accents and 
> slurs. Lily seems to prefer to put accents above slurs, while most music I 
> typeset seems to be the other way round.
>
> Unless ... I haven't tried this, but would using phrasing slurs rather than 
> slurs get round this - I don't think I've yet had to mix normal and phrasing 
> slurs...
>
> Cheers,
> Wol
>
> -----Original Message-----
> From: address@hidden [mailto:address@hidden On Behalf Of Mats Bengtsson
> Sent: 14 September 2006 07:59
> To: Trevor Bača
> Cc: lilypond-user
> Subject: Re: Stacking lyrics above dynamics?
>
> One possibility is to typeset the dynamics in a context of its own,
> for example using the \Dynamics context definition from the example
> "Piano centered dynamics" in the manual.
>
>    /Mats
>
> Trevor Bača wrote:
>   
> > Hi,
> >
> > Sane engraving rules position lyrics vertically below dynamics.
> >
> > Is there a way to reverse this, ie, to position dynamics vertically
> > below lyrics? (The "lyrics" in this score aren't lyrics at all, but
> > another stratum of information showing a different musical parameter
> > altogether.)
> >
> > Here's the snippet i've been working with:
> >
> > %%% BEGIN TOY SNIPPET %%%
> >
> > \version "2.9.16"
> >
> > \new Staff \with {
> >   \override DynamicLineSpanner #'staff-padding = #10
> > } <<
> >   \new Voice \with {
> >   } {
> >      \times 4/5 {
> >         c'4\f
> >         c'4\f
> >         c'4\f
> >         c'4\f
> >         c'4\f
> >      }
> >   }
> >   \new Lyrics \with {
> >      %\override VerticalAxisGroup #'minimum-Y-extent = #'(-30 . -40)
> >      %\override VerticalAxisGroup #'staff-padding = #50
> >   } \lyricmode {
> >      foo4 * 4/5
> >      foo4 * 4/5
> >      foo4 * 4/5
> >      foo4 * 4/5
> >      foo4 * 4/5
> >   }
> >     
> > %%% END TOY SNIPPET %%%
> >
> > I'm able to push the dynamics down to where I want them by setting the
> > staff-padding attribute of the DynamicLineSpanner grob. But moving the
> > lyrics up *above* the dynamics is proving to be really tricky.
> >
> > (I've been toying with the VerticalAxisGroup grob in the Lyrics
> > context, but all I've been able to do is create padding on either side
> > of the lyrics, rather than moving the lyrics above the dynamics.
> > Intuitively, it seems like there should be some way to declare a
> > stacking order of the different strata within a staff ("first
> > dynamics, then lyrics, going down the page") and it seems like maybe
> > the VerticalAlignment grob should be the place to set this up, but I
> > can't seem to tweak it.)
> >
> > So any tricks for moving lyrics up above dynamics?
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > lilypond-user mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/lilypond-user
> >   
> >     
>
>   

--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================