Re: Strange beaming error

2016-01-07 Thread Urs Liska
Am 07.01.2016 um 10:16 schrieb David Kastrup: > Urs Liska writes: > >> Do you also have subdivideBeams = ##t somewhere? >> If so please show the result with both 2.19.28 and .35.. >> >> And if that's the case you should maybe send me (privately?) the full >> piece so I

Re: Strange beaming error

2016-01-07 Thread David Kastrup
Urs Liska writes: > Before testing further I assume the current issue is due to *not* > using the latest state (which isn't in a release yet). Why are there different states? Did the original plan fail on paper or did it never reach paper? Or was it not correctly

Re: Strange beaming error

2016-01-07 Thread Urs Liska
Am 7. Januar 2016 10:16:29 MEZ, schrieb David Kastrup : >Urs Liska writes: > >> Do you also have subdivideBeams = ##t somewhere? >> If so please show the result with both 2.19.28 and .35.. >> >> And if that's the case you should maybe send me (privately?) the

Re: Strange beaming error

2016-01-07 Thread David Kastrup
Chris Yate writes: > On 7 January 2016 at 00:49, Thomas Morley wrote: > >> Btw, your images are inline _not_ attached. >> > > Are inlined images not OK here? ...or were you just being pedantic? > ;-) They were inlined into the HTML part only

Re: Strange beaming error

2016-01-07 Thread David Kastrup
Urs Liska writes: > Do you also have subdivideBeams = ##t somewhere? > If so please show the result with both 2.19.28 and .35.. > > And if that's the case you should maybe send me (privately?) the full > piece so I could test with several builds before and after several >

RE: Strange beaming error

2016-01-07 Thread Chris Yate
On 7 Jan 2016 1:31 am, "Mark Stephen Mrotek" wrote: > > Chris: > > > What is the time signature? 6/8? > > Or is it 2/4 grouped as if in tuplets? > Mark Mark, Yes, it's 6/8. Although it changes to 4/4 for one movement - the one before this problem occurs (that may or may

Re: Strange beaming error

2016-01-07 Thread Chris Yate
On 7 January 2016 at 17:12, Mark Stephen Mrotek wrote: > Chris, > > > > As I mentioned in a previous reply, make sure that identical “\set > Timining” instructions are in both the upper and lower staff. > > Once this is done, recompile and check for accuracy. > > > > Mark >

Re: Strange beaming error

2016-01-07 Thread Urs Liska
Am 07.01.2016 um 18:24 schrieb Chris Yate: > On 7 January 2016 at 17:12, Mark Stephen Mrotek > wrote: > > Chris, > > > > As I mentioned in a previous reply, make sure that identical “\set > Timining” instructions are in both

Re: Strange beaming error

2016-01-07 Thread Urs Liska
Hi Chris, 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

Re: Strange beaming error

2016-01-06 Thread Thomas Morley
2016-01-07 0:53 GMT+01:00 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) r8 > c,16 g' c, g' bf, g' > \clef bass > } > > I have a suspicion this may have something to do

RE: Strange beaming error

2016-01-06 Thread Mark Stephen Mrotek
] On Behalf Of Chris Yate Sent: Wednesday, January 06, 2016 4:17 PM To: Lilypond-User Mailing List <lilypond-user@gnu.org> 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

Re: Strange beaming error

2016-01-06 Thread Chris Yate
On 6 January 2016 at 23:53, Chris Yate 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

Re: Strange beaming error

2016-01-06 Thread Chris Yate
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). [image: Inline images 1] On 6 January 2016 at 23:59, Chris Yate wrote: >

Re: Strange beaming error

2016-01-06 Thread Chris Yate
On 7 January 2016 at 00:49, Thomas Morley wrote: > > 2016-01-07 0:53 GMT+01:00 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) r8 >> c,16

RE: Strange beaming error

2016-01-06 Thread Mark Stephen Mrotek
Morley <thomasmorle...@gmail.com> Cc: Lilypond-User Mailing List <lilypond-user@gnu.org> Subject: Re: Strange beaming error On 7 January 2016 at 00:49, Thomas Morley <thomasmorle...@gmail.com <mailto:thomasmorle...@gmail.com> > wrote: 2016-01-07 0:53 GMT+01:00 Chris Y

Re: Strange beaming error

2016-01-06 Thread Urs Liska
Do you also have subdivideBeams = ##t somewhere? If so please show the result with both 2.19.28 and .35.. And if that's the case you should maybe send me (privately?) the full piece so I could test with several builds before and after several recent changes. Urs Am 7. Januar 2016 01:16:43