Re: Fix issue 4355 -- broken beam subdivision (issue 226700043 by address@hidden)

[Urs Liska]

Am 25.04.2015 um 13:54 schrieb Benkő Pál:
> 2015-04-25 10:20 GMT+02:00  <address@hidden>:
> > Thank you for picking this up. It is certainly an improvement already.
> >
> > However: In an example where 8 32th notes are subdivided by 16th notes
> > ony the first and third subdivision should have two beams, the second
> > one only one beam.
> >
> > Put differently: when there is following a total of an eighth note's
> > worth there should be only one beam, even when that total is itself
> > subdivided into two sixteenth notes. (Presumably that logic should be
> > propagated to the situation of (nested shorter notes): when 16 64th
> > notes are subdivided by 32ths the divisions should should have the
> > following number of beams: 3-2-3-1-3-2-3.
> could you formulate this more generally?
> e.g. what to do with 12 32th notes?

I think I have explained it in a generic way in my subsequent replies. 
But generally:
Any given subdivision point should be handled according to the largest 
possible moment that follows.

12 32th notes amount to 3/8, so there are three 1-beam divisions. (Which 
is the current behaviour when baseMoment is 1/8 too.)
If baseMoment is 1/16 then additionally we should have 2-beam divisions 
between the 1-beam divisions at 1/8 and 2/8.

So the beaming pattern for 12 32rd notes with baseMoment 1/16 should be: 
2-1-2-1-2

x-x-x-x-x-x-x-x-x-x-x-x
|-|-|-| |-|-|-| |-|-|-|
|-| |-| |-| |-| |-| |-|


The beaming pattern for 64th notes with baseMoment 1/32 would be:

x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-etc.
|-|-|-|-|-|-|-| |-|-|-|-|-|-|-| |
|-|-|-| |-|-|-| |-|-|-| |-|-|-| |
|-| |-| |-| |-| |-| |-| |-| |-| |


> p
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel