[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Triple slurring
From: |
Simon Albrecht |
Subject: |
Re: Triple slurring |
Date: |
Mon, 11 Dec 2017 15:09:47 +0100 |
Am 11-Dec-2017 14:56:40 +0100 schrieb address@hidden:
Am 11.12.2017 um 10:08 schrieb David Kastrup:
> David Kastrup <address@hidden> writes:
>
>> Urs Liska <address@hidden> writes:
>>
>>> I'm encountering triple slurs like in the attached
>>> examples. Discussion came to the conclusion that I should not
>>> "modernize" the notation using only one slur but regard it as an
>>> expressive means.
>>> Any ideas?
>>> (And particularly ideas that also work with LilyPond 2.18?)
>> spanner-id (only as string) was introduced in version 2.15.5. The
>> convenient way of setting it via \= is a 2.19 thing, but you can do the
>> same with a function of your own or manually.
> Oh um, that will give you three slurs. They will still be attached to
> the whole chord, so not overly useful. You'll either need extensive
> slur coordinate manipulation,
That means using my "fake polyphony" together with \shape, isn't it?
Probably it's the best I should do in the current case.
> or you'll have to rely on 2.19 for
> in-chord slurs (which can be attached to single notes) after all.
>
Could you give me an example? I'm not sure I see what you mean.
\version "2.19"
{
<c\= 1 ( e\= 2 ( g\= 3 ( >4
<b\= 1 ) d\= 2 ) as\= 3 ) >
}
in conjunction with shape...
Best Simon