Hello Gilles, Thanks again for your reply and for putting me in the right direction!
Considering your question: "why use the <<...>> construct?": it was the only way of getting an error-free compilation of the composition. Your question however triggered something and after a while I noticed a minor difference in my notation. I added the duration of the notes of the chord to the first note of the chord, so within the <<..>>. In that case compilation only is error-free using the double marks <<..>>. And then obviously the [<<..>> <..>>] construct is not valid. I moved the duration of the notes outside the marks using the single marks <..> and now it works fine! Thanks again. Gerard -----Oorspronkelijk bericht----- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Gilles Sadowski Verzonden: maandag 15 september 2008 20:45 Aan: lilypond-user@gnu.org Onderwerp: Re: How to split autobeam Hi. > Here's one example that produces the wrong beaming: > > right = \context Voice = "discant" > > { > > \clef violin > > \time 4/4 > > \relative b' { <<b8. d fis b>> <<bes,16 d f bes>> <<b,8 d fis b>> > <<b,8 d fis b>> > > <<cis,8 eis gis cis>> <<cis,8 eis gis cis>> <<d,8 f a d>> <<d,8 f a > d>> }| > > } Hmm, this is still not a complete code: The \score part is missing. Why do you use the << ... >> construct? A chord is created with something like <c e g>4 I.e. with single brackets. Also, the duration is specified after the closing bracket. > The compiler produces the correct beaming between the b8. and bes,16 > chord and between the two b,8 chords. > > With the default auto-beam setting the next 4 chords are beamed > together. In this case the cis,8 chords should > > Be beamed together and the two d,8 chords should be beamed. You didn't tell why the solution I proposed does not satisfy your needs. Similarly to my previous post, your code above can turned into: %--- right = \context Voice = "discant"{ \clef violin \time 4/4 \relative b' { <b d fis b>8. <bes d f bes>16 <b d fis b>8 <b, d fis b>8 <cis eis gis cis>8[ <cis eis gis cis>8] <d f a d>8[ <d f a d>8] | } } \score { \right } %--- See attached pdf. > I've tried severla options, for example adding \nobeam to the first > d,8 chord. As a result the last two chords are > > Beamed together, but the first two chords (cis,8) are then separated, > not beamed. I agree that this behaviour looks strange. Maybe someone else can give an explanation or confirm that this is a bug. > Also tried overriding the default auto-beam, but that didnot produce > the correct result (yet). In this, I guess that the default behaviour should be what you expect, without resorting to this. > Hope you can help or point me in the direction where to look for a > solution. Again, what's wrong with using square (beaming) brackets? Something like a8[ b] c[ d] produces the right result. Gilles _____ Mijn Postvak In wordt beschermd door SPAMfighter 12922 spam-mails zijn er tot op heden geblokkeerd. Download de gratis SPAMfighter <http://www.spamfighter.com/lnl> vandaag nog! _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user