lilypond-user
[Top][All Lists]
Advanced

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

Re: Positioning Dynamics Contexts


From: Kevin Barry
Subject: Re: Positioning Dynamics Contexts
Date: Tue, 4 Aug 2015 18:18:42 +0100

On Tue, Aug 4, 2015 at 5:08 PM, Cynthia Karl <address@hidden> wrote:
> Shouldn’t the line:
>
>         \new Staff << \dynamicsAHigh \musicA \dynamicsALow >>
>
> resullt in the ordering in the score:
>
>         dynamicsAHigh
>         musicA
>         dynamicsALow

No: the result is that they are all part of the same Staff, and
dynamics are positioned below a staff by default - when they are not
in their own context (and you can't, as David pointed out, put a
Dynamics context inside a Staff context). In your example there is no
need to specify "\new Dynamics" - really you are just adding a voice
that contains spacer rests and dynamics (A Dynamics context is not
necessary). Assuming you still want to keep the notes and dynamics in
separate variables the code below should do what you want. Note the
two places where I replaced a caret ^ with an underscore _ to put text
below the Staff. I would also recommend giving some consideration to
merging the high and low dynamics variables (obviously it depends on
your score, but I can't imagine many scores where it is desirable to
separate them like that).

\version "2.18.2"

PocoAccel = {
     \override TextSpanner.bound-details.left.text = "poco accel."
}

musicA = \relative c'' {    \repeat unfold 16 c4     }
dynamicsAHigh = {    s1^AHigh s \PocoAccel s\startTextSpan
s\stopTextSpan        }
dynamicsALow  = {    s1_ALow  s\p  s s\f        }
musicB = \relative c'' {    \repeat unfold 16 b4   }
dynamicsBHigh = {   s1^BHigh s^"espress." s s }
dynamicsBLow =  {   s1_BLow  s\f s s }

\score {
    \new StaffGroup <<
        \new Staff << \dynamicsAHigh \musicA \dynamicsALow >>
        \new Staff << \dynamicsBHigh \musicB \dynamicsBLow>>
    >>
}



reply via email to

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