RE: Strange beaming error

[Mark Stephen Mrotek]

Chris:

 

What is the time signature? 6/8?

Or is it 2/4 grouped as if in tuplets?

 

Mark

 

From: address@hidden [mailto:address@hidden On Behalf Of Chris Yate
Sent: Wednesday, January 06, 2016 5:21 PM
To: Thomas Morley <address@hidden>
Cc: Lilypond-User Mailing List <address@hidden>
Subject: Re: Strange beaming error

 

 

On 7 January 2016 at 00:49, Thomas Morley <address@hidden> wrote:

 

2016-01-07 0:53 GMT+01:00 Chris Yate <address@hidden>:

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

 

 

 Hi Thomas, 

 

Without tiny example everyone can guess only.

 

Yes, I appreciate that -- I wasn't  able to get a minimal working example. I was hoping for any general suggestions to fix or known bugs that might cause this.

 

It's ~200 bars of music, over 5 files, so if necessary I'll put it up on a Gist. 

 

Btw, your images are inline _not_ attached.

 

Are inlined images not OK here? ...or were you just being pedantic? ;-)

 

Chris