lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Phrasing slurs shortened when broken


From: Urs Liska
Subject: Re: Phrasing slurs shortened when broken
Date: Mon, 17 Oct 2016 00:08:38 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0


Am 16.10.2016 um 23:48 schrieb David Kastrup:
> Javier Ruiz-Alma <address@hidden> writes:
>
>> In a piece I'm working on, and only from bar 146 on, slurs which are
>> broken across systems, the first broken slur will be typeset short for
>> a reason I can't figure out.What could exclusively affect the length
>> of the first segment of broken slurs?Changing from PhrasingSlur to
>> Slur makes no difference.I'm stumped.The version is 2.18.2.
> Looks like the clef change in the lower system has something to do with
> it.

This is probably right, so would that qualify as a bug?

To Javier:
There is the \shape function to handle that for you
(http://lilypond.org/doc/v2.18/Documentation/notation/modifying-shapes).
You can pass this function one or more sets of control point offsets as
shown in the following example. Actually you wouldn't need to do it that
way, as when you give only one set of points they will only be applied
to the first sibling.

HTH
Urs


%%%%%%%%%%%%%%%%%%%%%%%%
\version "2.19.49"

\paper {
  ragged-right = ##t
}

top = \relative c'' {
  \time 6/8
  r4. r8
 
  \shape #'(((0 . 0)(0 . 0)(2 . 1)(3 . 0))
            ((0 . 0)(0 . 0)(0 . 0)(0 . 0))) PhrasingSlur
  c \( f ~ |
  \break
 
  f16 e bes c es des \)
}

bottom = {
  r4. r4.
  \clef bass
  r4.
}

\score {
  <<
    \new PianoStaff <<
      \new Staff \top
      \new Staff \bottom
    >>
  >>
}
%%%%%%%%%%%%%%%%%%%%%%%%%




reply via email to

[Prev in Thread] Current Thread [Next in Thread]