Issue 60 in lilypond: beam multiplicity changing on rests

2008-06-13 Thread codesite-noreply
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 own

Re: Issue 60 in lilypond: beam multiplicity changing on rests

2008-06-08 Thread Joe Neeman
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 t

Issue 60 in lilypond: beam multiplicity changing on rests

2008-06-08 Thread codesite-noreply
Issue 60: beam multiplicity changing on rests http://code.google.com/p/lilypond/issues/detail?id=60 Comment #5 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_49 -- You received this message because you are liste

Re: Issue 60 in lilypond: beam multiplicity changing on rests

2008-06-05 Thread Han-Wen Nienhuys
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 strong opinions regarding beamlets and a > largish example to

Re: Issue 60 in lilypond: beam multiplicity changing on rests

2008-06-04 Thread Joe Neeman
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 strong opinions regarding beamlets and a largish example to test? We seem to be fairly close to releasing a sta

Issue 60 in lilypond: beam multiplicity changing on rests

2008-06-04 Thread codesite-noreply
Issue 60: beam multiplicity changing on rests http://code.google.com/p/lilypond/issues/detail?id=60 Comment #4 by lemzwerg: The old one IMHO. Reason: The length of the `longest' element under the beam (in the case of the second beam it's the r16 rest) should not have a larger `value' than the

Re: Issue 60 in lilypond: beam multiplicity changing on rests

2008-06-04 Thread Mats Bengtsson
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 in lilypond: beam multiplicity changing on rests

2008-06-04 Thread codesite-noreply
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 output

Issue 60 in lilypond: beam multiplicity changing on rests

2008-05-30 Thread codesite-noreply
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 is