Issue 60: beam multiplicity changing on rests
http://code.google.com/p/lilypond/issues/detail?id=60
Comment #6 by v.villenave:
Great! This one has been waiting for quite a while :-)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the
On Fri, 2008-06-06 at 00:11 -0300, Han-Wen Nienhuys wrote:
2008/6/4 Joe Neeman [EMAIL PROTECTED]:
Thanks Werner and Mats for the comments. I've made some further changes
to give the output that Werner suggested and to fix, in addition, bugs
489 and 599.
Is there anyone out there with
Issue 60: beam multiplicity changing on rests
http://code.google.com/p/lilypond/issues/detail?id=60
Comment #3 by joeneeman:
I've made some changes to beaming patterns in the dev/jneeman branch.
This improves
the results in many situations, but there is one in which I'm not sure
what the
While you are looking at the beaming rules. Have you by chance looked
into the
code that deals with subdivided beams. If so, could you also take a look
at issues 11, 489
and 599? There have also been several discussions on the mailing list
related to
the strange interaction between beatLength,
Issue 60: beam multiplicity changing on rests
http://code.google.com/p/lilypond/issues/detail?id=60
Comment #2 by v.villenave:
(Reproduced with 2.11.47 -- even though I don't really understand the problem)
--
You received this message because you are listed in the owner
or CC fields of this