lilypond-user
[Top][All Lists]
Advanced

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

Re: horizontal beams


From: James Lowe
Subject: Re: horizontal beams
Date: Sat, 22 Jan 2011 11:37:09 +0000
User-agent: Microsoft-MacOutlook/14.2.0.101115

Hello

-----Original Message-----
From: "address@hidden" <address@hidden>
Date: Sat, 22 Jan 2011 08:57:02 -0200
To: "address@hidden" <address@hidden>
Subject: RE: horizontal beams

>
>> I don't know how the code works, but as someone who browses the LSR
>> I would just say that there is only one tweak needed, but you are
>> implying there are cases when you need more than one tweak.
>
>
>i'm not implying, i'm saying it quite explicitly. and i sent a
>complete example demonstrating it: the tweak \override Beam #'damping
>= #+inf.0 fails in certain cases, although i haven't been able to find
>any logic as to when.
>
>i'm also saying is that adding the two overrides suggested by dmytro
>hasn't failed so far.
>
>finally, what i'm trying to say as clearly as possible, is that since
>this tweak is shown in snippets both in the LSR and the NR, i think
>the documentation should be updated somehow, perhaps with a warning
>that it may fail and that extra tweaks might be necessary.
>
>what i really think is that this tweak looks more like a buggy hack.
>
>

Then I think we might need to find out if \override Beam #'damping  =
#+inf.0 without any extra tweaks *should* work in all cases or not. If it
should then we have a bug and it should be reported as such.

If it doesn't in all cases then we can modify the LSR with, hopefully some
explanation.

So (and I apologise if you had already done this) can you provide the .ly
file you have where the \override Beam #'damping = #+inf.0 isn't enough?

It might not be a tiny example but it would be a start I think and we can
start to involve the dev-list.

Sorry to labour this, but I think it's important we get it right rather
than guess and make edits to snippets that are not right only to have to
change them back again later.

regards

James



>




reply via email to

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