|
From: | Victor Eijkhout |
Subject: | Re: beam breaking in tuplets |
Date: | Sun, 5 Nov 2006 18:04:06 -0600 |
I don't think you want that. Just try this: \relative c'' { \time 3/4 #(override-auto-beam-setting '(end * * * *) 3 16) #(override-auto-beam-setting '(end * * * *) 6 16) #(override-auto-beam-setting '(end * * * *) 9 16) \times 3/4 { r4 g8 a16 bes a8 bes16 c d8 c16 bes } | r4 g8 a16 bes a16 bes c8 | } \version "2.9.27" Bad side effects.But I think this approach points to a design error. Beam breaking is a visual operation, not a mathematical one. I want a sixteenth beam broken at any beat boundary, no matter whether this is in 4/4 time or in a 27 over 26 fragment.
Imho, of course.Btw, that raises another question I''ve been meaning to ask: do assignments have scope? Can I limit this beam setting overriding to one fragment, without explicitly restoring the old rules? (Lilypond looks so much like TeX that I would really expect such a mechanism to exist.)
Victor. On Nov 5, 2006, at 3:22 PM, Mats Bengtsson wrote:
If you divide a 3/4 measure into 4 equal beats, then each beat will be 3/16 long. So, you can obtain what you want with #(override-auto- beam-setting '(end * * * *) 3 16)#(override-auto-beam-setting '(end * * * *) 6 16) #(override-auto-beam-setting '(end * * * *) 9 16) Since this is a fairly uncommon rhythm, LilyPond does not specify any such default behaviour. /Mats Quoting Victor Eijkhout <address@hidden>:Is this a bug or a feature? (2.9.27, PPC) \relative c'' { \time 3/4 \times 3/4 { r4 g8 a16 bes a8 bes16 c d8 c16 bes } | #(override-auto-beam-setting '(end 1 16 * *) 2 4) r4 g8 a16 bes a8 bes16 c | }I was expecting the beam in the tuplet to be broken the same way as in the measure after.If I was expecting wrong, I'd appreciate a hint as to how to force this behaviour.Victor. _______________________________________________ lilypond-user mailing list address@hidden http://lists.gnu.org/mailman/listinfo/lilypond-user
[Prev in Thread] | Current Thread | [Next in Thread] |