lilypond-devel
[Top][All Lists]
Advanced

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

Re: Give slurs skylines in outside-staff-priority calculations. (issue 5


From: Janek Warchoł
Subject: Re: Give slurs skylines in outside-staff-priority calculations. (issue 5504055)
Date: Sun, 25 Dec 2011 22:50:21 +0100

Hi Mike,

(i've come back finally) When i was thinking about LilyPond lately, i
decided that changing character outlines from boxes to something more
precise was perhaps the most important thing we should improve now -
and i see that you are working on this! Great!
My (quick) question is: would be easy to apply your solution to other
objects?  I know that lyrics and dynamics really need improvement in
this area too - see this example: http://www.sendspace.com/file/dm4ua2
(source is attached to pdf).

Many thanks!
Janek

2011/12/21 address@hidden <address@hidden>:
> On Dec 21, 2011, at 6:11 PM, address@hidden wrote:
>
>> Mike, have you done any work to examine the effect of the value of
>> n_boxes on a) computation time, and b) quality of engraving fit?  If
>> there is no effect on computation time, then we might as well err on the
>> side of too many.  If there is a significant effect on computation time,
>> we ought to be careful to set the number as small as possible.
>>
>
> I ran this :
>
> \repeat unfold 100 {
>  \override Slur #'skyline-quantizing = #FOO
>  f'8^"rit" ( c'' f'' c''' f''') r r4 |
>  c'''2( c'' |
>  g'1)  ~ \startTrillSpan g'\stopTrillSpan g'\f( g)
> }
>
> Where FOO ranged from 1 to 19.  The time of compilation ranged from 20.23 to 
> 20.64 seconds and I didn't really see any difference above 10 boxes.  I'll 
> reduce the default to 10.
>
>> Also, in keeping with the desire to use full-word variable names,
>> perhaps box_count would be better than n_boxes.
>
> Will do.
>
> Cheers,
> MS
>
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel



reply via email to

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