Werner,

My reading would be

\version "2.24.3"
\relative c'' {
  d4 r16 f d b g'4~ g16 a c a64 (g fis g) |
}

It corrects only one beaming "error", is more rhythmically consistent, and 
might be more in keeping with the context.

Mark 

-----Original Message-----
From: lilypond-user-bounces+carsonmark=ca.rr....@gnu.org 
<lilypond-user-bounces+carsonmark=ca.rr....@gnu.org> On Behalf Of Werner LEMBERG
Sent: Tuesday, July 2, 2024 9:33 PM
To: sripedia_getp...@slmail.me
Cc: lilypond-user@gnu.org
Subject: Re: beam subdivision problem


Hello Jason,


> > ```
> > {
> >   \once \set subdivideBeams = ##t
> >   \once \set minimumBeamSubdivisionInterval = \musicLength 8
> >   f'16 f'32
> >       \set stemRightBeamCount = 2
> >             f'
> >       \set stemLeftBeamCount = 2
> >                f' f' f' f'
> > }
> > ```
> 
> Looks like this won't be possible without manually setting the beam 
> count.

OK, thanks.

> My beam subdivision algorithm tries to strictly respect metric values 
> as subdivision is intended to ease readers' track of the current 
> measure position. Adding features that loosen that strictness such as 
> one to support your desired output may allow composers to 
> unintentionally confuse readers, [...]

Well, this beam notation is not my invention but rather found in existing 
scores.  The specific subdivision was taken from Henle's Urtext version of 
Händel's violin sonata in g minor HWV 368, bar 2.

  https://www.henle.de/de/7-Sonaten-fuer-Violine-und-Generalbass/HN-191#

I guess the very reason for using this kind of subdivision is to make it 
resemble the first edition's incorrect beaming as much as possible (see 
attached image).

> Nevertheless, it may be simple enough to make a new context property 
> that defines ab offset for # of beamlets while still respecting the 
> value of `minimumBeamSubdivisionInterval`. So in your case, that new 
> context property would be 1 (must be a whole number).

Sounds very promising!  I'm waiting for your Merge Request :-)


    Werner


Reply via email to