Chris:
My experience in setting piano music is that the “\set Timing” instruction must be in both voices. If you have not done so, that might be the cause. Mark From: [email protected] [mailto:[email protected]] On Behalf Of Chris Yate Sent: Wednesday, January 06, 2016 4:17 PM To: Lilypond-User Mailing List <[email protected]> Subject: Re: Strange beaming error Further problems. I commented out the Time settings and here's more, this time in the RH (note paired semiquavers in LH here, which would be in sixes). This is now built with revision 35 (the latest). On 6 January 2016 at 23:59, Chris Yate <[email protected] <mailto:[email protected]> > wrote: On 6 January 2016 at 23:53, Chris Yate <[email protected] <mailto:[email protected]> > wrote: Hi, I'm wondering whether anyone can shed some light on the attached image. LH of the piano here is: { bf,16 (ef g8) r8 c,16 g' c, g' bf, g' \clef bass } I have a suspicion this may have something to do with the Timing / beat moment and beat structure, but it's inconclusive. This section of the music has: \set Timing.baseMoment = #(ly:make-moment 1/16) \set Timing.beatStructure = #'( 6 6 ) There are no barline errors, but I'm seeing this in the output quite a lot: programming error: mis-predicted force, 108.120472 ~= 101.465263 continuing, cross fingers programming error: mis-predicted force, 108.120472 ~= 105.654382 continuing, cross fingers programming error: mis-predicted force, 108.120472 ~= 101.465263 continuing, cross fingers Previously I was getting a similar issue where I had bars of 6 quavers, which were grouped in 3's -- and the middle of the second group was getting a spurious semiquaver beam. I seem to fixed it, though I'm not sure what the cause was. Thanks in advance, Chris P.S. Using Lilypond 2.19.28.
_______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
