bug-lilypond
[Top][All Lists]
Advanced

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

Re: ugly chord ties with short notes (32) in polyphony


From: Colin Hall
Subject: Re: ugly chord ties with short notes (32) in polyphony
Date: Wed, 20 Mar 2013 10:31:50 +0000
User-agent: mu4e 0.9.9.5-dev6; emacs 24.2.1

Eluze writes:

> janek.lilypond wrote
>> Hi,
>> 
>> On Tue, Mar 19, 2013 at 7:07 PM, Eluze <
>
>> eluzew@
>
>> > wrote:
>>> if you introduce 32nds in the end of the first voice the tie on the b
>>> looks
>>> ugly:
>>>
>>> \simultaneous {
>>>   \relative {<g' b e>4~
>> <g b e>
>> 8  e'16 e32 e}
>>>   \\
>>>   \relative {e,8 e e e}
>>> }
>> 
>> I'm pretty sure that the change in tie formatting isn't related to the
>> mere presence of 32nd notes, but to the fact that the overall spacing
>> changes.
>
> which is supported by the next example:
>
> \simultaneous {
>   \relative {<g' b e>4~<g b e>8  e'16 e r2 | <g, b e>4~<g b e>8  e'16 e r2}
>   \\
>   \relative {\textLengthOn e,8 e _"123" e  e r2 e8 e _"1234" e  e r2}
> }
>
>> Anyway, the easiest fix is probably to override tie-configuration
>> property of TieColumn (i think it's explained somewhere in the docs)
>> 
>> In general, the amount of bad tie formatting i see from Lily is
>> worrisome...  I have several dozens of ugly cases collected.  I wish i
>> had the time to finish my Tie report.
>
> thanks for that quick reply and workaround!
>
> should this be added to a tracker (I believe there's material enough
> there?!)

These examples for a collection of test cases for any future tie
implementation, so I think it is a good idea to keep them around.

Yes, there are plenty of trackers for ugly ties already:

https://code.google.com/p/lilypond/issues/list?can=2&q=tie+type%3Augly

with this one specific to chords:

https://code.google.com/p/lilypond/issues/detail?id=2368

So I'll log in and add a link to this thread from issue 2368.

Thanks for the bug report.

In summary, this problem with ties is a known issue.

Cheers,
Colin.

-- 
Colin Hall



reply via email to

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