>> The Alain and Rachmaninov only have one fewer beam, so the beam
>> count between the groups is not appropriate for the lengths of the
>> subdivided groups, according to the Gould rules. Personally, I
>> think the Gould rules are correct, but two of the music publishers
>> in your example do no
On 04.07.24 19:00, Carl Sorensen wrote:
The Alain and Rachmaninov only have one fewer beam, so the beam count
between the groups is not appropriate for the lengths of the
subdivided groups, according to the Gould rules. Personally, I think
the Gould rules are correct, but two of the music publ
On 2024-07-04 09:09, Jason Yip - sripedia_getpgrp(a)slmail.me wrote:
On 2024-07-03 22:06, Werner LEMBERG - wl(a)gnu.org wrote:
Even though you want this special subdivision at just one point in
your example, do you have examples where this special subdivision
occurs at multiple points in the sam
On Wed, Jul 3, 2024 at 11:07 PM Werner LEMBERG wrote:
>
> OK, here are some scans that I've found. As you can see, this kind of
> subdivision is not so special as previously assumed.
>
> * Jehan Alain, trois danses – Deuils (for organ), (publisher: Leduc)
>
> * Prokofiev, piano sonata 7, op. 83,
On 2024-07-03 22:06, Werner LEMBERG - wl(a)gnu.org wrote:
Even though you want this special subdivision at just one point in
your example, do you have examples where this special subdivision
occurs at multiple points in the same beam? My former suggestion
acts as a offset of # of beamlets for eve
> I have thought of a probably better solution. Currently, if
> `minimumBeamSubdivisionInterval` > `maximumBeamSubdivisionInterval`,
> the algorithm basically pretends that `subdivideBeams` is false.
> What if I change the behavior of that case such that you can add
> `maximumBeamSubdivisionInterv
> This may be slightly less ugly, but it still requires a function
> call every place you want a beam subdivision:
Thanks!
Werner
On 2024-07-02 21:33, Werner LEMBERG - wl(a)gnu.org wrote:
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
On Tue, Jul 2, 2024 at 10:48 AM Werner LEMBERG wrote:
>
> Folks,
>
>
> how can I easily create a beam subdivision as shown in the attached
> image using the current development version 2.25.18? The solution I
> came up with is extremely ugly...
>
>
> Werner
>
> This may be slightly less ugly
> 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.
Thanks, but I'm not typesetting the sonata :-) It would be
ge-
From: 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,
> > ```
> > {
> &g
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
Replying from my current email address since the one you cc'd me is
abandoned, wish I could update the git commits' email addresses without
breaking changes haha.
On 2024-07-02 09:47, Werner LEMBERG 'wl at gnu.org' wrote:
``` { \once \set subdivideBeams = ##t \once \set
minimumBeamSubdivisionI
Folks,
how can I easily create a beam subdivision as shown in the attached
image using the current development version 2.25.18? The solution I
came up with is extremely ugly...
Werner
```
{
\once \set subdivideBeams = ##t
\once \set minimumBeamSubdivisionInterval = \musicLength 8
14 matches
Mail list logo
