Re: Reusability of lilypond code?

[Torsten Hämmerle]

Hi Markus,

\tags are, as Aaron said, the way to go.

I'd just like to mention the way I often handle this, perhaps this is on any
help:

Instead of tagging each and every single dynamic element, I often completely
\omit certain stencils of a voice, if applicable.

The following example, while not being quite correct (because each voice
should get its own dynamics if they differ in any way), the DynamicText (and
Hairpin) stencils of hornII will be omitted in the score, the dynamics of
hornI will be used for both in the score and placed below the stave.
The parts keep their individual dynamics.

%%%%%%%%%%
\version "2.19.81"

hornI = { 
  \tag score \dynamicDown
  g'1\p\< ~ 1 ~ 1 ~ 1\f  
}
hornII = { 
  \tag score { \omit Voice.DynamicText \omit Voice.Hairpin }
  R1  c'\mp\< ~ 1 ~ 1\f 
}

\score {
  \new Staff \partcombine \hornI \hornII
}

\score {
  \new Staff \removeWithTag score \hornI
}

\score {
  \new Staff \removeWithTag score \hornII
}
%%%%%%%%%%

<http://lilypond.1069038.n5.nabble.com/file/t3887/tag-dynamics.png> 

HTH,
Torsten



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