Re: Issue 36 in lilypond: collision cresc and kneed beams

[lilypond]

Updates:
        Owner: ---
        Labels: -Priority-Low Priority-High

Comment #2 on issue 36 by percival.music.ca: collision cresc and kneed beams
http://code.google.com/p/lilypond/issues/detail?id=36

With our new definition of "High" as embarrassing, this qualifies.

It's not immediately obvious what the output *should* be, though... I guess  
the cresc
should be placed lower (to avoid the beam).  Maybe even use a whiteout  
outline around
the beam, and have the cresc draw before and after the beam?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings