Re: tie over clef change

[David Kastrup]

Dan Eble <dan@faithful.be> writes:

> On Sep 26, 2020, at 13:11, Hans Åberg <haberg-1@telia.com> wrote:
>> 
>>> 
>>> On 26 Sep 2020, at 18:50, Dan Eble <dan@faithful.be> wrote:
>>> 
>>> On Sep 26, 2020, at 12:34, Hans Åberg <haberg-1@telia.com> wrote:
>>>> 
>>>>> 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:
>>>>>> 
>>>>>> 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 think the question is answered from the musical point of view:
>> Werner's example is a tie since it is the same pitch, the same note
>> with longer value. In your example, the pitches are formally
>> different, and the difference is a comma in the Pythagorean tone
>> system, so it must be a slur.
>
> This sounds like an answer to a question I didn't ask.  I don't doubt
> that the arc in Werner's example is semantically a tie.  What I am
> wondering is what kind of LilyPond grob should represent the arc, and
> I'm thinking that it should be a Slur because of its shape, not a Tie
> because of its purpose.

Slur/Tie have graphical function, not musical function like stream
events.  So it's more a question of practicality than philosophy what to
use here, and it could even be something else like EnharmonicTie with
both slur-interface and tie-interface.

Tie endpoints tend to be different from slur endpoints since they
connect noteheads more than note columns (in-chord slurs are not really
a good reference since they currently suck with regard to their
positioning).

-- 
David Kastrup