Hi Andrew,
I can't compile your example on the mobile, but you are most certainly
experiencing an issue where LilyPond doesn't behave according to its declared
intention. (Assuming that with "broken" you mean subdivided).
The proper handling of subdivisions under tuplets is on my agenda in rewriting
the beaming pattern code, and this should be fixed in one of the next devel
releases.
Urs
Am 10. Februar 2016 12:35:53 MEZ, schrieb "N. Andrew Walsh"
<[email protected]>:
>Hi List,
>
>I have the following expression:
>
>\version "2.19.36"
>
>\relative c'' {
> \set subdivideBeams = ##t
> \set baseMoment = #(ly:make-moment 1/8)
> \set beatStructure = #'(2 2 2 2)
> \time 4/8
>\tuplet 3/2 { es,16\( f g } \tuplet 3/2 { a b cis\) } \tuplet 3/2 {
>dis\(
>eis g } a32 b16.->\) |
>}
>
>
>If I read the NR correctly, that should have broken every beam below
>the
>8th-note level, but the second group retains the 16th-note beam between
>the
>g in the last triplet and the a32 of the next group. It is correct in
>the
>first beat, breaking the 16th-note beams between the two triplets.
>
>Am I formatting this incorrectly? (spoiler: the answer is most
>certainly
>"yes," so I guess my question is thus more properly formulated "how am
>I
>formatting this incorrectly, and what is the correct syntax?")
>
>Cheers,
>
>A
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>lilypond-user mailing list
>[email protected]
>https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet._______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
