[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: chord name collide with staff
From: |
address@hidden |
Subject: |
Re: chord name collide with staff |
Date: |
Wed, 6 Feb 2013 08:37:57 +0100 |
On 6 févr. 2013, at 00:17, David Kastrup <address@hidden> wrote:
> "address@hidden" <address@hidden> writes:
>
>> Find #3 was wrong. There should have been no suicides in this precise
>> case. LilyPond just does not know how to do spacing on empty
>> skylines. This makes sense, as it is difficult to estimate the
>> distance between something and nothing. So, I'll use my previous
>> solution of flattening the skyline to 0 with a nice comment.
>
> That sounds nonsensical. A skyline should be able to contain empty
> stretches or be completely empty; that should be "neutral", namely let
> any neighboring skyline take over. A skyline flattened to 0, however,
> will kill the neighboring skyline and replace it with its
> maximum/minimum.
>
Good call. I think the problem is that the empty skyline is the lowermost, so
it impacts system-system spacing with the neighboring system. Not sure how
yet...
Cheers,
MS
- Re: chord name collide with staff, address@hidden, 2013/02/05
- Re: chord name collide with staff, David Kastrup, 2013/02/05
- Re: chord name collide with staff, David Kastrup, 2013/02/05
- Re: chord name collide with staff, address@hidden, 2013/02/05
- Re: chord name collide with staff, address@hidden, 2013/02/05
- Re: chord name collide with staff, address@hidden, 2013/02/05
- Re: chord name collide with staff, address@hidden, 2013/02/05
- Re: chord name collide with staff, David Kastrup, 2013/02/05
- Re: chord name collide with staff,
address@hidden <=
- Re: chord name collide with staff, David Kastrup, 2013/02/06
Re: chord name collide with staff, Colin Hall, 2013/02/16