Re: Beams not connecting

[Mats Bengtsson]

Graham: Note, new(?) bug report below!

Hans, have you read the full section on "Setting automatic
beam behavior"?. At the end, it mentions the beatGrouping
property, which can be used to determine the desired beaming. For 
example, in your 7/16 example, just add
 \set beatGrouping = #'(3 4)
to get what you want. Similarly, you can use
 \set beatGrouping = #'(3 4 3 4 4 3 4)
in your 25/16 example.

The result is also affected by the beatLength property, see
"Manual beams".

The true bug, in my opinion, is that beams are subdivided, even though 
subdivideBeams is set to ##f (which it is by
default). This is related to bug report #11, for example, but has 
nothing to do with triplets. See for example, the following
example.

\version "2.11.33"
\paper{ ragged-right=##t }
\relative c' {
 \time 6/8
 c8 c c16 c d8 d16 d d8 |  e8. e16 e e f8 f16 f8 f16 \break
 \set Timing.beatLength = #(ly:make-moment 3 8)
 c8 c c16 c d8 d16 d d8 |  e8. e16 e e f8 f16 f8 f16 }

I have not been able to find any setting of beatLength or beatGrouping 
or anything else that gives a full beam
(without any subdivisions) for both the rhythms d8 d16 d d8
and e8. e16 e e .

We have had several related bug reports, for example
issues #105 and #438, but none seems to pinpoint the basic
fact that setting subdivideBeams to false (which is the
default) still produces subdivided beams.

In addition, the exact interaction between beatLength, beatGrouping, 
automatic beaming and beam subdivision is a mystery to me and I suspect 
that there may be more
bugs hidden here, as for example is illustrated by
my example above.


  /Mats

Quoting Hans Aberg <address@hidden>:

> On 8 Oct 2007, at 08:13, Graham Percival wrote:
>
> > Hans, I was looking for an easier-to-understand example.  I have  
> > added it to the tracker, but please have a look at the example I  
> > added for hints about future bug reports.
> >
> > http://code.google.com/p/lilypond/issues/detail?id=489
>
> Yes, I see what you want, and I have rewritten it, as well making two 
>  other examples in meters 7/16 and 11/16 (these are common meters in  
> Bulgaria, and the 25/16 can be viewed as being compound of them).
>
> The bug is not about 25/16 specifically, but it seems to occur in any 
>  situation where the two 1/16 notes to be connected do not fall 
> within  a segment if the measure is divided into 1/8s (starting at 
> the  beginning of the measure). This may happen with these complex 
> meters,  but others have experienced with n-tuplets, as recently in 
> the  LilyPond Users list for quintuplets.
>
> ----
> \version "2.11.33"
> \paper{ ragged-right=##t }
> \relative c' {
>   \time 7/16
>   #(override-auto-beam-setting '(end * * 7 16) 3 16)
>   c16 c c  e8 e16 e |
>   d16 d d  f f f f |
> }
> ----
> \version "2.11.33"
> \paper{ ragged-right=##t }
> \relative c' {
>   \time 11/16
>   #(override-auto-beam-setting '(end * * 11 16) 4 16)
>   #(override-auto-beam-setting '(end * * 11 16) 7 16)
>   e8 e16 e  c c c  e8 e16 e |
>   d16 d d d  d d d  f f f f |
> }
> ----
> \version "2.11.33"
> \paper{ ragged-right=##t }
> \relative c' {
>   \time 25/16
>   #(override-auto-beam-setting '(end * * 25 16) 3 16)
>   #(override-auto-beam-setting '(end * * 25 16) 7 16)
>   #(override-auto-beam-setting '(end * * 25 16) 10 16)
>   #(override-auto-beam-setting '(end * * 25 16) 14 16)
>   #(override-auto-beam-setting '(end * * 25 16) 18 16)
>   #(override-auto-beam-setting '(end * * 25 16) 21 16)
>   c16 c c   e8 e16 e
>   c16 c c   e8 e16 e
>   e8 e16 e  c c c  e8 e16 e |
>   d16 d d  d d d d
>   d16 d d  d d d d
>   d16 d d d  d d d  f f f f |
> }
> ----
>
>
>
>
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-lilypond