On 3/2/07, Arvid Grøtting <[EMAIL PROTECTED]> wrote:
David Feuer <david.feuer <at> gmail.com> writes:> > \override DynamicText #'X-offset = #-2 > > Ooh! Neat! For some reason, this only seems to work for some of the > dynamics. They all move to the left, but only some of them move down. Yes; it all depends on whether LilyPond thinks they'll fit. > Is there a way to tell LilyPond to force them down, even if it thinks > they'll collide? You may want to specify other X-offsets \once in a while, to fit the dynamics into natural spaces. Also note that LilyPond will try to line up all dynamics and crescendi/decrescendi. (Is there a way to turn this off?) If all else fails, search the manuals for #'extra-offset, but use it sparingly. > Also, do you happen to know how to bring dynamic > marks a bit closer to the staff by default? I'm not quite sure, but read the fine manual; it's probably in there. > Finally, are there any > other overrides you suggest for vocal pieces? Oh, lots. If you have two voices on one staff, you want something like this: #(set-accidental-style 'modern-voice) You'll use ChoirStaff, so to read measure numbers try this: \override Score.BarNumber #'padding = #3 Unless you prefer the modern style, you'll say this: \set Score.autoBeaming = ##f If you have "on-and-off" lyrics, you may want this: \override Score.VerticalAxisGroup #'remove-first = ##t This of course depends on proper use of this: \context { \RemoveEmptyStaffContext } Here's a few more tricks: \new Staff = "tenors" \with { \override VerticalAxisGroup #'keep-fixed-while-stretching = ##t } << \clef "treble_8" \set Staff.instrumentName = \markup{ vcenter "Tenor " \column { \hcenter "I" \hcenter "II"}} You'll want #'keep-fixed-while-stretching to be ##t on any staff that has lyrics attached above it, and #'keep-fixed-while-stretching = ##f on lyrics that are above a staff, not below another. Lyrics example: \new Lyrics \with { alignAboveContext=tenors \override VerticalAxisGroup #'keep-fixed-while-stretching = ##f } \lyricsto tenori \tiWords Also, vocal voices tend to do things, ehm, differently, so I have these instead of \oneVoice, \voiceOne and \voiceTwo: songVoice = { \dynamicUp \phrasingSlurUp \slurUp \override TextScript #'direction = #1 } songVoiceOne = { \songVoice \override RepeatTie #'direction = #1 \voiceOne } songVoiceTwo = { \dynamicDown \phrasingSlurDown \override TextScript #'direction = #-1 \override RepeatTie #'direction = #-1 \voiceTwo } That's it for tricks currently in use, I think. This is with 2.11.20, by the way; earlier versions may need other tricks...
Can these please go into the manual under vocal music? -- Trevor Bača [EMAIL PROTECTED]
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
