lilypond-user
[Top][All Lists]
Advanced

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

Re: cross-staff phrasing (slur)


From: MING TSANG
Subject: Re: cross-staff phrasing (slur)
Date: Wed, 4 Sep 2013 16:42:48 -0700 (PDT)

Hi, Urs and Helge Kruse (sorry Helge - don't have your email address)

I managed to code cross staff phrasing with \change Staff = "right" or "left" with Helge's sample code.  I added other cross staff slurs.

Please refer to the attached. I coded bar 31, 35 and 121; but for bar 115 118 and 119 - I have time coding it.  Help is appreciated.

Thanks,
Ming



  
Date: Wed, 04 Sep 2013 16:54:15 +0200
From: Urs Liska <address@hidden>
To: MING TSANG <address@hidden>
Cc: "address@hidden" <address@hidden>
Subject: Re: cross-staff phrasing (slur)
Message-ID: <address@hidden>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

Am 04.09.2013 16:17, schrieb MING TSANG:
> Hi, Urs:
>
> Thank you for the info pertain to phrasing slurs.  I don't know how to
> code \change Staff in context staff (I have not use context Staff
> before) in my score which has 122 bars and there are 6 bars that has
> cross staff phrasing. I use \new Staff on my score.

You don't need to do that at that level.
If you write music that is printed in the "right" staff you can write
(at any time):

\change Staff = "left"

and then the current voice will continue in the other staff.
For your examples (of the first post) you would not write [half bar rest
+ half bar music] in one and [half bar music + half bar rest] in the
other staff but write the whole phrase in one voice and let it cross the
staff as I have described.
This way you can write the slur without problems.

> I also have difficulty to adapt the snippet
>
>
>      Setting the control points of a slur manually
>      <http://lsr.dsi.unimi.it/LSR/Item?id=134> [0.07280]
>
You don't need this snippet anymore. By now there is the function \shape
in LilyPond that lets you define _offsets_ from LilyPond's decision.
So you don't have to find the absolute offsets but can work from
LilyPond's default engraving.

Use
\shape list-of-offsets grob, that is for example

\shape #'((0 . 1)(0 . 0)(0 . 0)(0 . 0)) PhrasingSlur

for tweaking a phrasing slur to have its starting point '1' higher than
default.

HTH
Urs

> I have completed the 122-bar score without the phrasing slurs on bars
> 31,35, 115, 118, 119 & 121. Please refer to the attached .ly and .pdf
> ------------------------------------------------------------------------
>
>  3. Re:cross-staff phrasing (slur) (Urs Liska)
>
>
> Message: 3
> Date: Tue, 03 Sep 2013 19:30:53 +0200
> From: Urs Liska <address@hidden <mailto:address@hidden>>
> To: address@hidden <mailto:address@hidden>
> Subject: Re: cross-staff phrasing (slur)
> Message-ID: <address@hidden
> <mailto:address@hidden>>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> Am 03.09.2013 14:22, schrieb MING TSANG:
> > Dear lilyponders:
> >
> > I search LSR and cannot find help about cross-staff phrasing
> > engraving.  Is it possible in lilypond? Please refer to attached .png.
> > Cross phrasing (slur) in in measure 118, 119 & 121.  Lily coding is in
> > forever-thanks_T.ly ( no cross staff phrasing). Help is appreciated.
> >
> > Thank you for the help.
> > Ming
>
> Hi Ming,
>
> I don't have the time right now to give you a ready solution, but it's
> quite simple to do in LilyPond.
> As pphrasing slurs can only be done within one voice context you have to
> write the phrase in one voice.
> This voice will cross the staves with \change Staff = "right" (or
> "left"), while you should 'mute' the other voice with spacer rests.
>
> HTH
> Urs
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/lilypond-user/attachments/20130904/1be80a0c/attachment.html>

------------------------------

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user


End of lilypond-user Digest, Vol 130, Issue 24
**********************************************


Attachment: forever-thanks_T.ly
Description: Text Data

Attachment: forever-thanks_T.pdf
Description: Adobe PDF document


reply via email to

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