Re: nested beaming
> On 11 Apr 2024, at 17:14, Carl Sorensen wrote: > >> On Thu, Apr 11, 2024 at 6:44 AM Hans Åberg wrote: >> >> > On 10 Apr 2024, at 16:54, Carl Sorensen wrote: >> > >> > On Tue, Apr 9, 2024 at 10:23 AM Hans Åberg wrote: >> > >> >> In the past, it was possible to give 9/16 the beat structure [[2 2] [2 >> >> 3]], as a 2/4 with an extra 1/16 at the end, like in the Bulgarian >> >> Daichovo, but currently it is only possible with [4 2 3] as in: >> >> \time 9/16 >> >> \set beatStructure = #'(4 2 3) >> >> Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read. >> >> >> > Can you tell me a version where you could do this, and provide some sample >> > code that uses it? >> >> I have an old comment in a .ly file that I once wrote, but it does not tell >> the LilyPond version it was usable in, as the file has been updated: >> >> \tempo 4 = 120 >> \time 11/16 >> \set beatStructure = #'(4 3 4) >> >> % Old beam settings: >> % \overrideBeamSettings #'Score #'(11 . 16) #'end #'((* . (4 3 4))) >> % \set beatGrouping = #'(2 2 3 2 2) >> % \set subdivideBeams = ##t >> % #(override-auto-beam-setting '(end * * 11 16) 4 16) >> % #(override-auto-beam-setting '(end * * 11 16) 7 16) >> % #(set-time-signature 11 16 '(4 3 4)) >> > Thank you for this file. This syntax makes sense to me (but I haven't > verified that it still works). I have never known the nested square brackets > for nested beams as an input syntax to work. > > I'll do some more investigation. This link says override-auto-beam-setting got removed probably in LilyPond 2.13. https://github.com/nsceaux/nenuvar/issues/7
Re: nested beaming
On Thu, Apr 11, 2024 at 6:44 AM Hans Åberg wrote: > > > On 10 Apr 2024, at 16:54, Carl Sorensen > wrote: > > > > On Tue, Apr 9, 2024 at 10:23 AM Hans Åberg wrote: > > > >> In the past, it was possible to give 9/16 the beat structure [[2 2] [2 > 3]], as a 2/4 with an extra 1/16 at the end, like in the Bulgarian > Daichovo, but currently it is only possible with [4 2 3] as in: > >> \time 9/16 > >> \set beatStructure = #'(4 2 3) > >> Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read. > >> > > Can you tell me a version where you could do this, and provide some > sample code that uses it? > > I have an old comment in a .ly file that I once wrote, but it does not > tell the LilyPond version it was usable in, as the file has been updated: > > \tempo 4 = 120 > \time 11/16 > \set beatStructure = #'(4 3 4) > > % Old beam settings: > % \overrideBeamSettings #'Score #'(11 . 16) #'end #'((* . (4 3 4))) > % \set beatGrouping = #'(2 2 3 2 2) > % \set subdivideBeams = ##t > % #(override-auto-beam-setting '(end * * 11 16) 4 16) > % #(override-auto-beam-setting '(end * * 11 16) 7 16) > % #(set-time-signature 11 16 '(4 3 4)) > > Thank you for this file. This syntax makes sense to me (but I haven't verified that it still works). I have never known the nested square brackets for nested beams as an input syntax to work. I'll do some more investigation. Thanks, Carl
Re: nested beaming
> On 10 Apr 2024, at 23:29, Carl Sorensen wrote:
>
>> On Wed, Apr 10, 2024 at 2:02 PM Hans Åberg wrote:
>>
>> There is actually one example of a naturally occurring meter, meaning it is
>> used regularly, where such a sub-beaming might be useful, namely, a form of
>> the Čoček in 9/8, 9 = 2+2+2+3, where 3 = 1+2. I wrote it as 2+2+2+1+2, but
>> it would be nice to write it as 2+2+2+(1+2).
>>
>> If I write
>> \time 9/8
>> \set beatStructure = 2,2,2,3
>> \set subdivideBeams = ##t
>> then it ends up with all 2 = 1+1, and 3 = 1+1+1.
>>
>> So such examples may occur even if there is not a composer trying to do
>> something special.
>
> So in the following, I think I get what you call 2+2+2+3, but unfortunately I
> don't get 3 = 1+2. Do you agree with this statement?
>
> I have made it a little better, because the 2 are all 2, but the three is
> just 3 (not 1+2)
>
> \version "2.25.11"
> {
>\time 9/8
>\set beatStructure = #'(2 2 2 3)
>\set subdivideBeams = ##t
>\set minimumBeamSubdivisionInterval = \musicLength 4
>\repeat unfold 18 a'16
> }
There is also the syntax
\time 2,2,2,3 9/16
instead of
\time 9/16
\set beatStructure = #'(2 2 2 3)
Perhaps it should be extended somehow.
Re: nested beaming
> On 10 Apr 2024, at 16:54, Carl Sorensen wrote: > > On Tue, Apr 9, 2024 at 10:23 AM Hans Åberg wrote: > >> In the past, it was possible to give 9/16 the beat structure [[2 2] [2 3]], >> as a 2/4 with an extra 1/16 at the end, like in the Bulgarian Daichovo, but >> currently it is only possible with [4 2 3] as in: >> \time 9/16 >> \set beatStructure = #'(4 2 3) >> Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read. >> > Can you tell me a version where you could do this, and provide some sample > code that uses it? I have an old comment in a .ly file that I once wrote, but it does not tell the LilyPond version it was usable in, as the file has been updated: \tempo 4 = 120 \time 11/16 \set beatStructure = #'(4 3 4) % Old beam settings: % \overrideBeamSettings #'Score #'(11 . 16) #'end #'((* . (4 3 4))) % \set beatGrouping = #'(2 2 3 2 2) % \set subdivideBeams = ##t % #(override-auto-beam-setting '(end * * 11 16) 4 16) % #(override-auto-beam-setting '(end * * 11 16) 7 16) % #(set-time-signature 11 16 '(4 3 4))
Re: nested beaming
> On 10 Apr 2024, at 23:29, Carl Sorensen wrote:
>
>> On Wed, Apr 10, 2024 at 2:02 PM Hans Åberg wrote:
>>
>>
>> There is actually one example of a naturally occurring meter, meaning it is
>> used regularly, where such a sub-beaming might be useful, namely, a form of
>> the Čoček in 9/8, 9 = 2+2+2+3, where 3 = 1+2. I wrote it as 2+2+2+1+2, but
>> it would be nice to write it as 2+2+2+(1+2).
>>
>> If I write
>> \time 9/8
>> \set beatStructure = 2,2,2,3
>> \set subdivideBeams = ##t
>> then it ends up with all 2 = 1+1, and 3 = 1+1+1.
>>
>> So such examples may occur even if there is not a composer trying to do
>> something special.
>>
>> So in the following, I think I get what you call 2+2+2+3, but unfortunately
>> I don't get 3 = 1+2. Do you agree with this statement?
Correct.
>> I have made it a little better, because the 2 are all 2, but the three is
>> just 3 (not 1+2)
>>
>> \version "2.25.11"
>> {
>>\time 9/8
>>\set beatStructure = #'(2 2 2 3)
>>\set subdivideBeams = ##t
>>\set minimumBeamSubdivisionInterval = \musicLength 4
>>\repeat unfold 18 a'16
>> }
If I write
{
\time 9/8
\set beatStructure = #'(2 2 2 3)
\set subdivideBeams = ##t
\set minimumBeamSubdivisionInterval = \musicLength 8
\repeat unfold 18 a'16
}
then I get the sub-beams, but should only be applied to the last 3, and between
the first 1/8 and the last 2/8.
Re: nested beaming
On Wed, Apr 10, 2024 at 2:02 PM Hans Åberg wrote:
>
>
> There is actually one example of a naturally occurring meter, meaning it
> is used regularly, where such a sub-beaming might be useful, namely, a form
> of the Čoček in 9/8, 9 = 2+2+2+3, where 3 = 1+2. I wrote it as 2+2+2+1+2,
> but it would be nice to write it as 2+2+2+(1+2).
>
> If I write
> \time 9/8
> \set beatStructure = 2,2,2,3
> \set subdivideBeams = ##t
> then it ends up with all 2 = 1+1, and 3 = 1+1+1.
>
> So such examples may occur even if there is not a composer trying to do
> something special.
So in the following, I think I get what you call 2+2+2+3, but unfortunately
I don't get 3 = 1+2. Do you agree with this statement?
I have made it a little better, because the 2 are all 2, but the three is
just 3 (not 1+2)
\version "2.25.11"
{
\time 9/8
\set beatStructure = #'(2 2 2 3)
\set subdivideBeams = ##t
\set minimumBeamSubdivisionInterval = \musicLength 4
\repeat unfold 18 a'16
}
Carl
Re: nested beaming
> On 10 Apr 2024, at 20:15, Carl Sorensen wrote:
>
> Forwarding to keep on list.
>
> On Wed, Apr 10, 2024 at 11:35 AM Hans Åberg wrote:
>
> > On 10 Apr 2024, at 19:00, Carl Sorensen wrote:
> >
> > On Wed, Apr 10, 2024 at 10:22 AM Hans Åberg wrote:
> >
> > > So is the issue that you would like to have the final [2 3] beamed with a
> > > pair of beamed 16th notes joined to a trio of beamed sixteenth notes by a
> > > single beam?
> >
> > Yes.
> >
> > This works out of the box now, as 4+5 with subdivisions and 4+3 with
> > subdivisions
> >
> > \version "2.25.11"
> > {
> >\time 9/16
> >\set beatStructure = #'(4 5)
> >\set subdivideBeams = ##t
> >\repeat unfold 9 a'16
> >
> >\time 7/16
> >\set beatStructure = 4,3
> >\repeat unfold 7 a'16
> > }
>
> This works for the 9=(2+2)+(2+3); I attach a file that compiles, in case you
> want to check. I need to check the 7/16 later. One could also have the 3 in
> other places. like 9 = (2+2)+(3+2) or (3+2)+(2+2). They exist in Turkey and
> Macedonia in slower forms without the sub-beaming, but in theory, it is
> possible.
>
> I think that it will not work if you want to subdivide with the 3 in the
> first position. I can imagine that there could be some sort of flag that
> would allow it to work correctly with the 3 in the first position, but that
> will require some extra development. If you think it's important, I could
> ping Jason Yip (who did the new autobeam functionality) to see if he has any
> ideas about it.
There is actually one example of a naturally occurring meter, meaning it is
used regularly, where such a sub-beaming might be useful, namely, a form of the
Čoček in 9/8, 9 = 2+2+2+3, where 3 = 1+2. I wrote it as 2+2+2+1+2, but it would
be nice to write it as 2+2+2+(1+2).
If I write
\time 9/8
\set beatStructure = 2,2,2,3
\set subdivideBeams = ##t
then it ends up with all 2 = 1+1, and 3 = 1+1+1.
So such examples may occur even if there is not a composer trying to do
something special.
Re: nested beaming
[Adding back to list] On Wed, Apr 10, 2024 at 9:23 AM Paul Scott wrote: > Version 2.25.14 > > Are there parameters to change? It would seem that there would several > possibilities even though I got the one I wanted this time. > > Paul > > > You can read about the parameters in the 2.25 Notation Reference: https://lilypond.org/doc/v2.25/Documentation/notation/setting-automatic-beam-behavior See the selected snippet Subdividing Beams Carl
Re: nested beaming
Forwarding to keep on list.
On Wed, Apr 10, 2024 at 11:35 AM Hans Åberg wrote:
>
> > On 10 Apr 2024, at 19:00, Carl Sorensen
> wrote:
> >
> > On Wed, Apr 10, 2024 at 10:22 AM Hans Åberg wrote:
> >
> > > So is the issue that you would like to have the final [2 3] beamed
> with a pair of beamed 16th notes joined to a trio of beamed sixteenth notes
> by a single beam?
> >
> > Yes.
> >
> > This works out of the box now, as 4+5 with subdivisions and 4+3 with
> subdivisions
> >
> > \version "2.25.11"
> > {
> >\time 9/16
> >\set beatStructure = #'(4 5)
> >\set subdivideBeams = ##t
> >\repeat unfold 9 a'16
> >
> >\time 7/16
> >\set beatStructure = 4,3
> >\repeat unfold 7 a'16
> > }
>
> This works for the 9=(2+2)+(2+3); I attach a file that compiles, in case
> you want to check. I need to check the 7/16 later. One could also have the
> 3 in other places. like 9 = (2+2)+(3+2) or (3+2)+(2+2). They exist in
> Turkey and Macedonia in slower forms without the sub-beaming, but in
> theory, it is possible.
>
I think that it will not work if you want to subdivide with the 3 in the
first position. I can imagine that there could be some sort of flag that
would allow it to work correctly with the 3 in the first position, but that
will require some extra development. If you think it's important, I could
ping Jason Yip (who did the new autobeam functionality) to see if he has
any ideas about it.
Thanks,
Carl
Re: nested beaming
> On 10 Apr 2024, at 17:13, Carl Sorensen wrote: > >> On Tue, Apr 9, 2024 at 10:23 AM Hans Åberg wrote: >> >>> On 8 Apr 2024, at 18:46, Simon Albrecht wrote: >>> >>> On 08.04.24 18:22, Paul Scott wrote: Many years ago I could nest square brackets in Lilypond. How can I write this now incorrect code: a16[[ 16 16] 16[ 16 16]] i.e. two groups of 3 beamed 16th notes joined by a single beam. >>> >>> The question is: what is the context and why do you want this? >> >> In the past, it was possible to give 9/16 the beat structure [[2 2] [2 3]], >> as a 2/4 with an extra 1/16 at the end, like in the Bulgarian Daichovo, but >> currently it is only possible with [4 2 3] as in: >> \time 9/16 >> \set beatStructure = #'(4 2 3) >> Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read. >> >>> Normally, this is called subdividing beams and there is a context property >>> to turn it on. This is explained in the NR at Rhythms -> Beams -> Setting >>> automatic beam behaviour (or similar). There have recently been significant >>> improvements to how LilyPond handles this, but IIRC it’s not fully ‘there’ >>> yet and in some situations manual intervention is needed besides defining >>> baseMoment etc. >> >> But this has not yet been implemented? > > So is the issue that you would like to have the final [2 3] beamed with a > pair of beamed 16th notes joined to a trio of beamed sixteenth notes by a > single beam? Yes. > I could see that such a notation might be easy to read, but it violates the > mathematical beaming convention since the two subgroups joined by the single > beam are not each 1/8 in duration. I'm not saying this notation is > incorrect; I'm just saying that to implement it we would need to bypass the > normal convention The meter is like 2/4 but with one extra 1/16 on the last 1/8 metric sub-accent (or sub-beat), so the final [2 3] should be beamed together to properly express the relationship: If using 4+2+3, it suggests that the two last metric beats are equal. Likewise, (2+2)+(3+2) is a different meter, and 4+5 with no sub-beaming on the 5 would not make clear the metric beat structure. One can do the opposite, take away 1/16 on the last beat, 7 = (2+2)+3, as in the Bulgarian rachenitsa. Then I use 7 = 4+3, which looks fine, but it does not show the sub-beat in the 4 = 2+2. Using 7 = 2+2+3 would be wrong, because that suggests the beats between the last 2 and 3 are about equal.
Re: nested beaming
> On 10 Apr 2024, at 16:54, Carl Sorensen wrote: > > On Tue, Apr 9, 2024 at 10:23 AM Hans Åberg wrote: > > In the past, it was possible to give 9/16 the beat structure [[2 2] [2 3]], > as a 2/4 with an extra 1/16 at the end, like in the Bulgarian Daichovo, but > currently it is only possible with [4 2 3] as in: > \time 9/16 > \set beatStructure = #'(4 2 3) > Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read. > > Can you tell me a version where you could do this, and provide some sample > code that uses it? It was so long time ago that I do not remember. The new interface is much simpler, so I felt it was not a crucial point. One sees sheet music with the beaming division 9 = 4+2+3. Bela Bartok used this meter, and it may have that latter written meter and beaming.
Re: nested beaming
On Tue, Apr 9, 2024 at 10:23 AM Hans Åberg wrote: > > > On 8 Apr 2024, at 18:46, Simon Albrecht wrote: > > > > On 08.04.24 18:22, Paul Scott wrote: > >> Many years ago I could nest square brackets in Lilypond. How can I > write this now incorrect code: > >> > >> a16[[ 16 16] 16[ 16 16]] i.e. two groups of 3 beamed 16th notes joined > by a single beam. > > > > The question is: what is the context and why do you want this? > > In the past, it was possible to give 9/16 the beat structure [[2 2] [2 > 3]], as a 2/4 with an extra 1/16 at the end, like in the Bulgarian > Daichovo, but currently it is only possible with [4 2 3] as in: > \time 9/16 > \set beatStructure = #'(4 2 3) > Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read. > > > Normally, this is called subdividing beams and there is a context > property to turn it on. This is explained in the NR at Rhythms -> Beams -> > Setting automatic beam behaviour (or similar). There have recently been > significant improvements to how LilyPond handles this, but IIRC it’s not > fully ‘there’ yet and in some situations manual intervention is needed > besides defining baseMoment etc. > > But this has not yet been implemented? > So is the issue that you would like to have the final [2 3] beamed with a pair of beamed 16th notes joined to a trio of beamed sixteenth notes by a single beam? I could see that such a notation might be easy to read, but it violates the mathematical beaming convention since the two subgroups joined by the single beam are not each 1/8 in duration. I'm not saying this notation is incorrect; I'm just saying that to implement it we would need to bypass the normal convention Thanks, Carl
Re: nested beaming
On Tue, Apr 9, 2024 at 10:23 AM Hans Åberg wrote: > > > > In the past, it was possible to give 9/16 the beat structure [[2 2] [2 > 3]], as a 2/4 with an extra 1/16 at the end, like in the Bulgarian > Daichovo, but currently it is only possible with [4 2 3] as in: > \time 9/16 > \set beatStructure = #'(4 2 3) > Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read. > Can you tell me a version where you could do this, and provide some sample code that uses it? Thanks, Carl
Re: Fwd: nested beaming
It looks like I was wrong about \set subdivideBeams = ##f canceling \set
subdivideBeams = ##t . It was another part in a score where it wasn't
canceled affect the line I was working on.
Paul
On 4/9/24 9:28 AM, Paul Scott wrote:
Forgot to send to list.
Forwarded Message
Subject:Re: nested beaming
Date: Tue, 9 Apr 2024 09:26:22 -0700
From: Paul Scott
To: Carl Sorensen
On 4/8/24 3:59 PM, Carl Sorensen wrote:
On Mon, Apr 8, 2024 at 4:51 PM Carl Sorensen
wrote:
On Mon, Apr 8, 2024 at 11:14 AM Paul Scott
wrote:
The case at the moment is with long groups of triplets of
which the
following is now a part:
{
\time 2/4
\tuplet 3/2 8 {
a'16 16 \set stemRightBeamCount = 1 16 \set
stemLeftBeamCount = 1
16 16 16
}
}
I think that after last summer's GSOC project on beaming,
this now works correctly out of the box:
My mistake. These changes didn't get in until 2.25
\version "2.25.11" % but earlier 2.25 versions may work
{
\time 2/4
\set subdivideBeams = ##t
\tuplet 3/2 8 {
a'16 16 16
16 16 16
}
}
Carl
It worked for the triplets but \set subdivideBeams = ##f doesn't turn
it off for following music.
Paul
Fwd: nested beaming
Forgot to send to list.
Forwarded Message
Subject:Re: nested beaming
Date: Tue, 9 Apr 2024 09:26:22 -0700
From: Paul Scott
To: Carl Sorensen
On 4/8/24 3:59 PM, Carl Sorensen wrote:
On Mon, Apr 8, 2024 at 4:51 PM Carl Sorensen
wrote:
On Mon, Apr 8, 2024 at 11:14 AM Paul Scott
wrote:
The case at the moment is with long groups of triplets of
which the
following is now a part:
{
\time 2/4
\tuplet 3/2 8 {
a'16 16 \set stemRightBeamCount = 1 16 \set
stemLeftBeamCount = 1
16 16 16
}
}
I think that after last summer's GSOC project on beaming, this
now works correctly out of the box:
My mistake. These changes didn't get in until 2.25
\version "2.25.11" % but earlier 2.25 versions may work
{
\time 2/4
\set subdivideBeams = ##t
\tuplet 3/2 8 {
a'16 16 16
16 16 16
}
}
Carl
It worked for the triplets but \set subdivideBeams = ##f doesn't turn it
off for following music.
Paul
Re: nested beaming
> On 8 Apr 2024, at 18:46, Simon Albrecht wrote: > > On 08.04.24 18:22, Paul Scott wrote: >> Many years ago I could nest square brackets in Lilypond. How can I write >> this now incorrect code: >> >> a16[[ 16 16] 16[ 16 16]] i.e. two groups of 3 beamed 16th notes joined by a >> single beam. > > The question is: what is the context and why do you want this? In the past, it was possible to give 9/16 the beat structure [[2 2] [2 3]], as a 2/4 with an extra 1/16 at the end, like in the Bulgarian Daichovo, but currently it is only possible with [4 2 3] as in: \time 9/16 \set beatStructure = #'(4 2 3) Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read. > Normally, this is called subdividing beams and there is a context property to > turn it on. This is explained in the NR at Rhythms -> Beams -> Setting > automatic beam behaviour (or similar). There have recently been significant > improvements to how LilyPond handles this, but IIRC it’s not fully ‘there’ > yet and in some situations manual intervention is needed besides defining > baseMoment etc. But this has not yet been implemented?
Re: nested beaming
Fortunately I always use the latest development version. I'll try this in a
while.Thank you!Paul Sent from my Galaxy
Original message From: Carl Sorensen
Date: 4/8/24 4:00 PM (GMT-07:00) To: Paul Scott
Cc: Simon Albrecht ,
Lilypond-User Mailing List , Jean Abou Samra
Subject: Re: nested beaming On Mon, Apr 8, 2024 at 4:51 PM
Carl Sorensen wrote:
On Mon, Apr 8, 2024 at 11:14 AM Paul Scott wrote:
The case at the moment is with long groups of triplets of which the
following is now a part:
{
\time 2/4
\tuplet 3/2 8 {
a'16 16 \set stemRightBeamCount = 1 16 \set stemLeftBeamCount = 1
16 16 16
}
}
I think that after last summer's GSOC project on beaming, this now works
correctly out of the box:
My mistake. These changes didn't get in until 2.25
\version "2.25.11" % but earlier 2.25 versions may work
{
\time 2/4
\set subdivideBeams = ##t
\tuplet 3/2 8 {
a'16 16 16
16 16 16
}
}
Carl
Re: nested beaming
On Mon, Apr 8, 2024 at 4:51 PM Carl Sorensen
wrote:
>
>
> On Mon, Apr 8, 2024 at 11:14 AM Paul Scott
> wrote:
>
>>
>> The case at the moment is with long groups of triplets of which the
>> following is now a part:
>>
>> {
>>\time 2/4
>>\tuplet 3/2 8 {
>> a'16 16 \set stemRightBeamCount = 1 16 \set stemLeftBeamCount = 1
>> 16 16 16
>>}
>> }
>>
>> I think that after last summer's GSOC project on beaming, this now works
>> correctly out of the box:
>
>
>
My mistake. These changes didn't get in until 2.25
> \version "2.25.11" % but earlier 2.25 versions may work
> {
>\time 2/4
>\set subdivideBeams = ##t
>\tuplet 3/2 8 {
> a'16 16 16
> 16 16 16
>}
> }
>
>
Carl
Re: nested beaming
On Mon, Apr 8, 2024 at 11:14 AM Paul Scott wrote:
>
> The case at the moment is with long groups of triplets of which the
> following is now a part:
>
> {
>\time 2/4
>\tuplet 3/2 8 {
> a'16 16 \set stemRightBeamCount = 1 16 \set stemLeftBeamCount = 1
> 16 16 16
>}
> }
>
> I think that after last summer's GSOC project on beaming, this now works
> correctly out of the box:
\version "2.24"
{
\time 2/4
\set subdivideBeams = ##t
\tuplet 3/2 8 {
a'16 16 16
16 16 16
}
}
HTH,
Carl
Re: nested beaming
On 4/8/24 9:46 AM, Simon Albrecht wrote:
On 08.04.24 18:22, Paul Scott wrote:
Many years ago I could nest square brackets in Lilypond. How can I
write this now incorrect code:
a16[[ 16 16] 16[ 16 16]] i.e. two groups of 3 beamed 16th notes
joined by a single beam.
The question is: what is the context and why do you want this?
The case at the moment is with long groups of triplets of which the
following is now a part:
{
\time 2/4
\tuplet 3/2 8 {
a'16 16 \set stemRightBeamCount = 1 16 \set stemLeftBeamCount = 1
16 16 16
}
}
Normally, this is called subdividing beams and there is a context
property to turn it on. This is explained in the NR at Rhythms ->
Beams -> Setting automatic beam behaviour (or similar).
I did look at NR 1.2.4
There have recently been significant improvements to how LilyPond
handles this, but IIRC it’s not fully ‘there’ yet and in some
situations manual intervention is needed besides defining baseMoment etc.
What Jean gave you is the fully manual version of this and may be
necessary for ‘non-standard’ notation.
My triplet example is definitely not non-standard unless for some reason
Gould doesn't like it.
I presume the old ability to nest brackets break something else somewhere.
Thank you,
Paul
Best, Simon
Re: nested beaming
On 08.04.24 18:22, Paul Scott wrote: Many years ago I could nest square brackets in Lilypond. How can I write this now incorrect code: a16[[ 16 16] 16[ 16 16]] i.e. two groups of 3 beamed 16th notes joined by a single beam. The question is: what is the context and why do you want this? Normally, this is called subdividing beams and there is a context property to turn it on. This is explained in the NR at Rhythms -> Beams -> Setting automatic beam behaviour (or similar). There have recently been significant improvements to how LilyPond handles this, but IIRC it’s not fully ‘there’ yet and in some situations manual intervention is needed besides defining baseMoment etc. What Jean gave you is the fully manual version of this and may be necessary for ‘non-standard’ notation. Best, Simon
Re: nested beaming
Le lundi 08 avril 2024 à 09:22 -0700, Paul Scott a écrit :
> Many years ago I could nest square brackets in Lilypond. How can I write
> this now incorrect code:
>
> a16[[ 16 16] 16[ 16 16]] i.e. two groups of 3 beamed 16th notes joined
> by a single beam.
>
> I have looked at NR 1,2,4
A little bit manual, but you can do
\version "2.24.2"
{
\time 6/8
a'16 16 \set stemRightBeamCount = 1 16 \set stemLeftBeamCount = 1 16 16 16
}
https://lilypond.org/doc/v2.24/Documentation/notation/beams.html#manual-beams
signature.asc
Description: This is a digitally signed message part
nested beaming
Many years ago I could nest square brackets in Lilypond. How can I write this now incorrect code: a16[[ 16 16] 16[ 16 16]] i.e. two groups of 3 beamed 16th notes joined by a single beam. I have looked at NR 1,2,4 TIA, Paul
