Re: Slurring across line breaks

[Glendan Lawler]

Hello, and thank you very much for your help.  The first one worked wonderfully, but I'm having a little bit of trouble getting the second thing to work.  Here is the function that I set up, based on the tweak to which you referred me with the modification you gave me:  


#(define (my-callback grob)
  (let* ((orig (ly:grob-original grob))        ; have we been split?
      
         (siblings (if (ly:grob? orig)         ; if yes, get the split pieces (our siblings)
                     (ly:spanner-broken-into orig) '() )))

   (if (and (>= (length siblings) 2)
             (eq? (car (last-pair siblings)) grob))
     (ly:grob-set-property! grob 'direction UP))))

breakTieUp = \override Tie #'after-line-breaking = #my-callback


And then here's how I used it:              a2. ~ \breakTieUp a2.~ \break 

Have I done this right?  Did I do something wrong?  It isn't giving me any errors, yet the output looks exactly the same >.<

Glendan

On Sat, Nov 21, 2009 at 2:37 PM, Neil Puttock <address@hidden> wrote:

2009/11/21 Glendan Lawler <address@hidden>:

> Hello, I'm having a problem with my slur, and I've looked everywhere and
> don't know how to fix it.  There is a line break and my slur is starting at
> the beginning of the staff, but my tie begins after the key signature.  It
> looks rather odd, and I would like to make it so that the slur begins where
> the tie begins.  Any ideas?

This is one of the most annoying bugs in LilyPond
(http://code.google.com/p/lilypond/issues/detail?id=379).  The usual
workaround (apart from really hairy manual curve hacking) is to use a
phrasing slur:

\(d4. \melisma cis8\) \melismaEnd

You'll need the explicit melisma commands since there's no equivalent
of slurMelismaBusy for phrasing slurs.

> Also, another problem I'm having:  is it possible to have a slur/tie go in
> different directions before and after the break?  In one part, I have a tie
> going down that crosses a break, but the note becomes the upper voice of a
> polyphonic split on the next line, so when the tie goes down on the next
> line, it looks like it belongs to the wrong voice and is rather confusing,
> but if I have all the ties going up, then the line above when there's still
> only one voice, it just looks stupid.  Any thoughts?

Try using the snippet from section 6.8 `Difficult tweaks' in the
Notation Reference:

http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Difficult-tweaks#Difficult-tweaks

You can substitute the 'extra-offset override for 'direction:

(ly:grob-set-property! grob 'direction UP)

Regards,
Neil