OK, I've now compiled your score (thanks for the gist, looks nice BTW) and went through the beaming issues I could see.
First of all I must say that the new subdivision logic (introduced in 2.19.35) seems to do what I wanted and is actually an improvement: Compare 01.png to 02.png and 03.png and tell me which one gives you a more immediate idea of the music ...
(and just in case anyone is in doubt: 01 is the new one and how it should be done, 02 is 2.19.34, and 03 is 2.19.19 (and any older version).
###
First issue I saw is shown in 04.png (m. 21)
Note that the music is in 6/8.
I'm not sure this qualifies as a bug as it is actually wrongly coded with
\set Timing.baseMoment = (ly:make-moment 1/16)
\set Timing.beatStructure = #'(6 6)
You should change that to
\set baseMoment = (ly:make-moment 1/8)
\set beatStructure = #'(3 3)
, then the result is correct as per 05.png.
But I suggest you don't subdivide here at all (as you have correctly do in the l.h.) - or if you would consider subdivisions as the way to go then at least do it in both hands.
###
However, a possible issue is shown in 06.png.
Here it may be wrong that the first beam has a beamlet instead of two beams. This is a case for David's suggestion to write down *all* rules. The issue is that the durations are the same as baseMoment - but here it is used correctly (other than with the first example). This notation is very useful if you have a single trailing note on a beam after a subdivision, but here it seems slightly strange.
###
I couldn't reproduce the issue shown in your initial message, though.
###
Is there any issue I overlooked?
Best
Urs
Am 07.01.2016 um 00:53 schrieb Chris
Yate:
Hi,
I'm wondering whether anyone can shed some light on the attached image.
LH of the piano here is:
{
bf,16 (ef g8) r8c,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
_______________________________________________ lilypond-user mailing list address@hidden https://lists.gnu.org/mailman/listinfo/lilypond-user
