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, beatGrouping, subdivideBeams and
the automatic beaming rules. In particular, it seems odd to me that you
can get
subdivided beams even though subdivideBeams is set to false.
An example of a relevant email thread is
http://lists.gnu.org/archive/html/bug-lilypond/2007-10/msg00056.html
I remember trying to dig into the code myself but never got the time to
digest it
enough to be able to fix any of these problems.
/Mats
[EMAIL PROTECTED] wrote:
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 should be. In the second beam of example2.xxx.png, which
version is correct?
Attachments:
example1.new.png 3.5 KB
example1.old.png 3.5 KB
example2.new.png 3.7 KB
example2.old.png 3.8 KB
Issue attribute updates:
Status: Started
--
=============================================
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond