Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals

[lilypond]

Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Medium Engraving-nitpick

New issue 898 by v.villenave: Enhancement: rests should be taken into  
account when determining beaming intervals
http://code.google.com/p/lilypond/issues/detail?id=898

The attached example shows that when preceded by a 16th rest, a dotted
eight is beamed to the following eights (which doesn't happen with a 16th
note instead of a rest).

\version "2.13.6"

\relative c' {
 % this shows the default beaming and how it should be beamed
 r16 c8. c8 c r16 c8. c8[ c] |
}

Ideally, "rests should be taken into account when determining the shortest
note in the beaming interval.  It should be a switchable option to preserve
the current behaviour and to accommodate both preferences, as I don't
believe there is a generally accepted rule here.", Trevor said.

"Issue 638 is related, as solutions to that and this require a different
approach to beaming - one which assesses the duration of notes
(and rests) within a whole bar before selecting the most appropriate
beaming for that bar."

Attachments:
        toto.png  2.7 KB

--
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