lilypond-user
[Top][All Lists]
Advanced

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

Re: tuplet slurs


From: David Nalesnik
Subject: Re: tuplet slurs
Date: Sat, 11 Feb 2017 13:43:31 -0600

On Sat, Feb 11, 2017 at 11:11 AM, Werner LEMBERG <address@hidden> wrote:
>
>>> For voices with lyrics it is common to put triplet indications
>>> always above the staff, using the following rules.
>>>
>>>   . stems up or down, no beam: as usual (i.e., a number and a
>>>      bracket at the top, as if using \tupletUp)
>>>
>>>    . stems up, with beam: as usual (i.e., a number over the beam)
>>>
>>> The last case, however, is unusual:
>>>
>>>    . stem down, with beam: a number and a *slur* at the top.
>
> BTW, these rules can be found in the vocal score of `Arabella' (by
> Richard Strauss), for example.
>
>> It strikes me that I've seen code somewhere that uses slurs instead of
>> brackets.  I find this:
>> http://www.lilypondforum.de/index.php?topic=1658.0
>
> Yes, I can remember that also – very nice!
>
>> The results look great, but of course, the slur is broken.  It might
>> not be hard to modify that routine to do what you want..
>
> Oh, I actually don't really care whether the slur is broken or not.
> I'm rather interested in having a lilypond option to make it behave
> (i.e., differentiate between tuplet slur and tuplet brackets) as
> outlined above.

I've attached a patch which permits tuplets with slurs instead of
brackets.  Sorry that you have to build LilyPond to use it.

It's pretty rough.  For one thing, the slur shapes for inclined slurs
are probably not ideal.

To get the bowed-tuplets, you set TupletBracket.tuplet-slur to #t.

You can move the slur closer/further from the number by setting
TupletNumber.padding to the value you'd like (default: 0.3).  Don't
know what other
consequences there might be when setting TupletNumber.padding, but I
don't want to add more properties unless it's really necessary.

To get the behavior you want, check the example file.  There is a
Scheme function which
should put your rules into effect.

>
>> [...]  Also, a full bracket might be used if the tuplet number
>> wouldn't intersect the bracket.  Maybe this should be default
>> behavior?  I know I've seen the bracket notation in Britten, albeit
>> without the tuplet number.
>
> I think making lilypond provide unbroken tuplet slurs and brackets is
> a welcome addition :-)

I'll look at this too.  Shouldn't be too hard.

Best,
David

Attachment: 0001-Allow-slurs-instead-of-brackets-with-tuplets.patch
Description: Text Data

Attachment: tuplet-test.ly
Description: Text Data


reply via email to

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