Dear Keith, thanks very much for Your very good explanations. I think, the best solution would be to write the dynamics in the lower staff, as You suggested.
2011/7/25 Keith OHara <k-ohara5...@oco.net> > On Mon, 25 Jul 2011 11:52:06 -0700, Stefan Thomas < > kontrapunktstefan@googlemail.**com <kontrapunktste...@googlemail.com>> > wrote: > > I thought I could also solve problem in the below quoted snippet with and >> >> override of minimum-Y-extent. But unfortunately, I get a bad collision >> between dynamics and and the next staff: >> > > The crescendo to ff spans a line of music that crosses staves. LilyPond > lets you cross any number of staves, but to do so she ignores collisions of > spanners that cross staves. You might want to use #(ly:set-option > 'debug-skylines) to see outlines of what items get space reserved for them. > > The crescendo runs through the ottava bracket even without the override. > Extending the ff downward with (-12 . 0) lowered the cresc. , but did not > push the next staff down because the ff is part of a line that Lilypond > believes is allowed to cross staves. > > I would place the dynamics in the lower primo staff > primoB = { \clef bass > \crescTextCresc > s2\< s8 s8\ff s4 > } > If you need the dynamics in their logical voice (for MIDI output?) the you > could use > \once\override DynamicLineSpanner #'Y-offset = #-19 > before the note with the \< to specify where you want the dynamics line > relative to the *upper* staff (its original staff). > > I recommend you use "\once" before any override of minimum-Y-extent, and > use it on items that are fixed to a staff. In this case the only solid item > I see is the last rest in secundoA > \once\override Rest #'minimum-Y-extent = #'(0 . 6) > r2 > > Four-hand modern piano music will be very frustrating, or maybe very > rewarding, to typeset.
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user