[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: tie over clef change
From: |
Hans Åberg |
Subject: |
Re: tie over clef change |
Date: |
Sat, 26 Sep 2020 18:34:41 +0200 |
> On 26 Sep 2020, at 18:04, Dan Eble <dan@faithful.be> wrote:
>
>> On Sep 26, 2020, at 09:41, Dan Eble <dan@faithful.be> wrote:
>>
>> On Sep 26, 2020, at 08:55, Werner LEMBERG <wl@gnu.org> wrote:
>>>
>>>
>>> Despite Gould's “incorrect” verdict, here is an example from an old UE
>>> edition of Liszt's “Liebestraum No. 1”, which demonstrates that ties
>>> over clef changes *do* happen and make sense sometimes...
>>>
>>> I still think that LilyPond should support that, handling the tie like
>>> a slur in this case.
>>
>> That's a very good example. It's hard to imagine any reasonable alternative.
>>
>> What kind of grob would an editor expect here? a Tie because it connects
>> notes of the same pitch, or a Slur because it connects notes at different
>> staff positions? (or something else?)
>
> I'll answer my own question. A tie from d♯ to e♭ generates a Tie grob, so
> for consistency, this should be a Tie that looks like a slur.
The notes d♯ to e♭ have different pitches in the staff notation system, which
cannot express E12 enharmonic equivalents, so this is slur. So it should be a
slur that looks like slur.
- tie over clef change, Werner LEMBERG, 2020/09/26
- Re: tie over clef change, Dan Eble, 2020/09/26
- Re: tie over clef change, Dan Eble, 2020/09/26
- Re: tie over clef change,
Hans Åberg <=
- Re: tie over clef change, Dan Eble, 2020/09/26
- Re: tie over clef change, Hans Åberg, 2020/09/26
- Re: tie over clef change, Dan Eble, 2020/09/26
- Re: tie over clef change, Hans Åberg, 2020/09/26
- Re: tie over clef change, David Kastrup, 2020/09/27
- Re: tie over clef change, Jean Abou Samra, 2020/09/27
- Re: tie over clef change, David Kastrup, 2020/09/27
- Re: tie over clef change, Werner LEMBERG, 2020/09/26
- Re: tie over clef change, Hans Åberg, 2020/09/26
- Re: tie over clef change, Kevin Barry, 2020/09/26