My first reaction on glancing at it was "yikes!" But it seems to cover exactly what I need. Thanks!
Ted On Wed, Feb 18, 2009 at 1:31 PM, Trevor Daniels <[email protected]> wrote: > Ted > > Section 5.5.4 in the Notation Reference describes how to modify the shape of > ties, slurs and phrasing slurs. It's a little tricky, but it's easy > compared with modifying the two parts of a slur split over a line break! > This is described in section 6.8 of the Notation Reference. You need to > combine the two, and this should enable you to achieve the shape you want. > > Good luck! > > Trevor > > ----- Original Message ----- From: "Ted Hopp" <[email protected]> > To: <[email protected]> > Sent: Wednesday, February 18, 2009 6:04 PM > Subject: Controlling slur shape across line breaks > > >> Is there a way to control the shape of a (phrasing) slur on each side >> of a line break? The attached image shows the awful layout that >> results from the following fragment: >> >> upper = \relative c' { >> \clef "treble" >> \phrasingSlurUp >> \partial 16 >> d16\( | \break >> e4 f g a | >> \time 6/4 >> \change Staff = "lower" \stemUp g4 f c1 \) \change Staff = "upper" >> \stemNeutral | >> \time 4/4 >> d4\( f <a, c e f>2 ~ | \break >> <a c e f>1 \) >> } >> >> lower = \relative c { >> \clef "bass" >> \partial 16 r16 | R1 | \time 6/4 R1. \time 4/4 R1*2 >> } >> >> \score { >> \new PianoStaff << >> \new Staff = "upper" \upper >> \new Staff = "lower" \lower >> >> >> \layout {} >> } >> >> As can be seen, both ends of the slur before the first line break >> needs to be raised. After the break, the start of the slur >> continuation (in measure 1) is good but the end (in measure 2) needs >> to be lowered (a lot!) and, once that is done, there needs to be a lot >> more curvature to avoid collision with the notes and the time change. >> A slightly different problem can be seen in measure 4, where the slur >> ends well but should start the measure much higher up. >> >> I need a way to fix problems like these by controlling the shape of >> slurs, and not, for instance, by changing to phrasingSlurDown (which >> doesn't work in the context in which these problems first showed up). >> > > > -------------------------------------------------------------------------------- > > >> _______________________________________________ >> lilypond-user mailing list >> [email protected] >> http://lists.gnu.org/mailman/listinfo/lilypond-user >> > > _______________________________________________ lilypond-user mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-user
