Re: Beam settings in 2.13.29
On 10 August 2010 01:08, Carl Sorensen c_soren...@byu.edu wrote: On 8/9/10 5:22 PM, Trevor Daniels t.dani...@treda.co.uk wrote: Neil Puttock wrote Monday, August 09, 2010 9:07 PM On 6 August 2010 20:36, Trevor Daniels t.dani...@treda.co.uk wrote: Second, this only seems to work in the Score context. I don't know if this is a bug or an error in the documentation. We'll have to wait for Carl to return from vacation to check this out. It is a bug, but one which I think will prove intractable for timeSignatureSettings, since the context inside \time is hard-coded (to the Timing alias): it only reads timeSignatureSettings at the Score level unless the Timing_translator's moved. Looks like the solution is a doc change to make this clear, then. Or perhaps we should change the context inside \time. I'll try to have a look at this this week. Carl, have you had time to investigate fixing this yet? It looks like a 2.14 release blocker to me. Cheers, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
On 12/15/10 3:43 PM, Neil Puttock n.putt...@gmail.com wrote: On 10 August 2010 01:08, Carl Sorensen c_soren...@byu.edu wrote: On 8/9/10 5:22 PM, Trevor Daniels t.dani...@treda.co.uk wrote: Neil Puttock wrote Monday, August 09, 2010 9:07 PM On 6 August 2010 20:36, Trevor Daniels t.dani...@treda.co.uk wrote: Second, this only seems to work in the Score context. I don't know if this is a bug or an error in the documentation. We'll have to wait for Carl to return from vacation to check this out. It is a bug, but one which I think will prove intractable for timeSignatureSettings, since the context inside \time is hard-coded (to the Timing alias): it only reads timeSignatureSettings at the Score level unless the Timing_translator's moved. Looks like the solution is a doc change to make this clear, then. Or perhaps we should change the context inside \time. I'll try to have a look at this this week. Carl, have you had time to investigate fixing this yet? I think the solution is a documentation change. timeSignatureSettings can only apply to the context containing the time signature, i.e. wherever the Timing_translator is. If we want to have beam settings set by the timeSignatureSettings property, and we want different time signatures in different staves, we will need to move the Timing_translator to the Staff context, instead of the Score context. I'll cook a patch to the documentation. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
On 16 December 2010 00:05, Carl Sorensen c_soren...@byu.edu wrote: I think the solution is a documentation change. timeSignatureSettings can only apply to the context containing the time signature, i.e. wherever the Timing_translator is. OK, though does that mean you're leaving the context arg in the music function? Cheers, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
On 12/15/10 3:43 PM, Neil Puttock n.putt...@gmail.com wrote: On 10 August 2010 01:08, Carl Sorensen c_soren...@byu.edu wrote: On 8/9/10 5:22 PM, Trevor Daniels t.dani...@treda.co.uk wrote: Neil Puttock wrote Monday, August 09, 2010 9:07 PM On 6 August 2010 20:36, Trevor Daniels t.dani...@treda.co.uk wrote: Second, this only seems to work in the Score context. I don't know if this is a bug or an error in the documentation. We'll have to wait for Carl to return from vacation to check this out. It is a bug, but one which I think will prove intractable for timeSignatureSettings, since the context inside \time is hard-coded (to the Timing alias): it only reads timeSignatureSettings at the Score level unless the Timing_translator's moved. Looks like the solution is a doc change to make this clear, then. Or perhaps we should change the context inside \time. I'll try to have a look at this this week. Carl, have you had time to investigate fixing this yet? Cancel my last answer. I had forgotten what was going on here. I can see that I have more work on this. It looks like a 2.14 release blocker to me. I agree. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
On Wed, Dec 15, 2010 at 05:19:27PM -0700, Carl Sorensen wrote: It looks like a 2.14 release blocker to me. I agree. Could we get an issue number? You don't need to have a tiny example or image, but I'd like to see something in the tracker to show that we have more than one critical issue. (unless you think you'll fix it today, in which case there's not much point opening an issue) Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
On 12/15/10 5:49 PM, Graham Percival gra...@percival-music.ca wrote: On Wed, Dec 15, 2010 at 05:19:27PM -0700, Carl Sorensen wrote: It looks like a 2.14 release blocker to me. I agree. Could we get an issue number? You don't need to have a tiny example or image, but I'd like to see something in the tracker to show that we have more than one critical issue. (unless you think you'll fix it today, in which case there's not much point opening an issue) Just added as issue 1456. The tiny example is actually necessary for the debug work, so it's up there, along with the png. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
On 6 August 2010 20:36, Trevor Daniels t.dani...@treda.co.uk wrote: Second, this only seems to work in the Score context. I don't know if this is a bug or an error in the documentation. We'll have to wait for Carl to return from vacation to check this out. It is a bug, but one which I think will prove intractable for timeSignatureSettings, since the context inside \time is hard-coded (to the Timing alias): it only reads timeSignatureSettings at the Score level unless the Timing_translator's moved. Cheers, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
Neil Puttock wrote Monday, August 09, 2010 9:07 PM On 6 August 2010 20:36, Trevor Daniels t.dani...@treda.co.uk wrote: Second, this only seems to work in the Score context. I don't know if this is a bug or an error in the documentation. We'll have to wait for Carl to return from vacation to check this out. It is a bug, but one which I think will prove intractable for timeSignatureSettings, since the context inside \time is hard-coded (to the Timing alias): it only reads timeSignatureSettings at the Score level unless the Timing_translator's moved. Looks like the solution is a doc change to make this clear, then. I'll leave it for Carl to pick up. Neil Thanks Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
On 8/9/10 5:22 PM, Trevor Daniels t.dani...@treda.co.uk wrote: Neil Puttock wrote Monday, August 09, 2010 9:07 PM On 6 August 2010 20:36, Trevor Daniels t.dani...@treda.co.uk wrote: Second, this only seems to work in the Score context. I don't know if this is a bug or an error in the documentation. We'll have to wait for Carl to return from vacation to check this out. It is a bug, but one which I think will prove intractable for timeSignatureSettings, since the context inside \time is hard-coded (to the Timing alias): it only reads timeSignatureSettings at the Score level unless the Timing_translator's moved. Looks like the solution is a doc change to make this clear, then. Or perhaps we should change the context inside \time. I'll try to have a look at this this week. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
Nick Payne wrote Saturday, August 07, 2010 12:22 AM
I also notice that when I turn off the beamExceptions the beaming
goes a
bit haywire. Have a look at bars 5 and 6 after I have used \set
beamExceptions = #'():
This is due to erroneous ly input; see below:
\version 2.13.29
changeBeamingA = \overrideTimeSignatureSettings
#'Score
#'(2 . 4) % time signature fraction
#'(1 . 8) % base moment fraction
#'(1)% beatStructure
This should be
#'(1 1 1 1) % base moment fraction
if you want beams grouped in quavers else only
the first 1/8 is a separate beam group.
Or, if you want the default to beam the whole bar you need
#'(1 . 2) % base moment fraction
#'(1)% beatStructure
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
changeBeamingB = \set beamExceptions =
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
revertBeaming = \set beamExceptions = #'()
\relative c'' {
\set tupletSpannerDuration = #(ly:make-moment 1 8)
\changeBeamingA
\time 2/4
\repeat unfold 8 c16
\times 2/3 { \repeat unfold 12 c16 }
\repeat unfold 16 c32
\times 4/6 { \repeat unfold 24 c32 }
\revertBeaming
\break \repeat unfold 8 c16 \repeat unfold 16 c32
\changeBeamingB
\repeat unfold 8 c16
\times 2/3 { \repeat unfold 12 c16 }
\repeat unfold 16 c32
\times 4/6 { \repeat unfold 24 c32 }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
Hi Nick
There are a couple of things which prevented your
override from working. Don't forget this is very new
code in a development release - you're probably the
first person to use it in anger, so you may find any
residual bugs.
First, the override command simply overrides the
*default* which will be used when invoked by any
later \time command, so the \time command must come
*after* \changeBeaming, not before.
Second, this only seems to work in the Score context.
I don't know if this is a bug or an error in the
documentation. We'll have to wait for Carl to return
from vacation to check this out.
Trevor
- Original Message -
From: Nick Payne nick.pa...@internode.on.net
To: Trevor Daniels t.dani...@treda.co.uk
Cc: lilypond-user lilypond-user@gnu.org
Sent: Thursday, August 05, 2010 1:03 PM
Subject: Re: Beam settings in 2.13.29
Thanks, that works. I assume the command to revert beaming to the
defaults is \set beamExceptions = #'()
I'd still like to understand why what I did with
overrideTimeSignatureSettings didn't work. From my reading of
s.1.2.3 of the notation manual it should have.
Nick
On 05/08/10 18:02, Trevor Daniels wrote:
Hi Nick
You got the hard bit right, but from 2.13.29 you can
use the simpler
changeBeaming = \set beamExceptions =
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
to change the beaming exceptions.
Trevor
- Original Message - From: Nick Payne
nick.pa...@internode.on.net
To: lilypond-user lilypond-user@gnu.org
Sent: Thursday, August 05, 2010 1:22 AM
Subject: Beam settings in 2.13.29
In 2/4 time, in earlier versions I used
changeBeaming = \overrideBeamSettings #'Voice #'(2 . 4) #'end
#'((* . (2))
((1 . 8) . (2 2))
((1 . 16) . (2 2 2 2))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)))
to get 16th and 32nd notes and tupletted 16th 32nd notes grouped
as I wanted, putting \changeBeaming in the voice where it's
needed.
2.13.29 convert-ly tells me that I need to change this manually
to use overrideTimeSignatureSettings or beamExceptions, but I'm
struggling to find an example that I can use as a base.
I tried changing my override to:
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4)
#'(1 . 4)
#'(1 1)
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)
the score builds without error and I get a PDF, but the beaming
is still the default - eg 32nd notes are beamed eight at a time.
Here's my short example. How do I get four beams per bar?
\version 2.13.29
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4) % time signature fraction
#'(1 . 4) % base moment fraction
#'(1 1)% beatStructure
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
\relative c'' {
\time 2/4
\changeBeaming
\repeat unfold 8 c16
\times 8/12 { \repeat unfold 12 c16 }
\repeat unfold 16 c32
\times 16/24 { \repeat unfold 24 c32 }
}
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
Yes, it works when used before the time signature when I use #'Score but
not when I use #'Voice.
I also notice that when I turn off the beamExceptions the beaming goes a
bit haywire. Have a look at bars 5 and 6 after I have used \set
beamExceptions = #'():
\version 2.13.29
changeBeamingA = \overrideTimeSignatureSettings
#'Score
#'(2 . 4) % time signature fraction
#'(1 . 8) % base moment fraction
#'(1)% beatStructure
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
changeBeamingB = \set beamExceptions =
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
revertBeaming = \set beamExceptions = #'()
\relative c'' {
\set tupletSpannerDuration = #(ly:make-moment 1 8)
\changeBeamingA
\time 2/4
\repeat unfold 8 c16
\times 2/3 { \repeat unfold 12 c16 }
\repeat unfold 16 c32
\times 4/6 { \repeat unfold 24 c32 }
\revertBeaming
\break \repeat unfold 8 c16 \repeat unfold 16 c32
\changeBeamingB
\repeat unfold 8 c16
\times 2/3 { \repeat unfold 12 c16 }
\repeat unfold 16 c32
\times 4/6 { \repeat unfold 24 c32 }
}
Nick
On 07/08/10 05:36, Trevor Daniels wrote:
Hi Nick
There are a couple of things which prevented your
override from working. Don't forget this is very new
code in a development release - you're probably the
first person to use it in anger, so you may find any
residual bugs.
First, the override command simply overrides the
*default* which will be used when invoked by any
later \time command, so the \time command must come
*after* \changeBeaming, not before.
Second, this only seems to work in the Score context.
I don't know if this is a bug or an error in the
documentation. We'll have to wait for Carl to return
from vacation to check this out.
Trevor
- Original Message - From: Nick Payne
nick.pa...@internode.on.net
To: Trevor Daniels t.dani...@treda.co.uk
Cc: lilypond-user lilypond-user@gnu.org
Sent: Thursday, August 05, 2010 1:03 PM
Subject: Re: Beam settings in 2.13.29
Thanks, that works. I assume the command to revert beaming to the
defaults is \set beamExceptions = #'()
I'd still like to understand why what I did with
overrideTimeSignatureSettings didn't work. From my reading of s.1.2.3
of the notation manual it should have.
Nick
On 05/08/10 18:02, Trevor Daniels wrote:
Hi Nick
You got the hard bit right, but from 2.13.29 you can
use the simpler
changeBeaming = \set beamExceptions =
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
to change the beaming exceptions.
Trevor
- Original Message - From: Nick Payne
nick.pa...@internode.on.net
To: lilypond-user lilypond-user@gnu.org
Sent: Thursday, August 05, 2010 1:22 AM
Subject: Beam settings in 2.13.29
In 2/4 time, in earlier versions I used
changeBeaming = \overrideBeamSettings #'Voice #'(2 . 4) #'end #'((*
. (2))
((1 . 8) . (2 2))
((1 . 16) . (2 2 2 2))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)))
to get 16th and 32nd notes and tupletted 16th 32nd notes grouped as
I wanted, putting \changeBeaming in the voice where it's needed.
2.13.29 convert-ly tells me that I need to change this manually to
use overrideTimeSignatureSettings or beamExceptions, but I'm
struggling to find an example that I can use as a base.
I tried changing my override to:
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4)
#'(1 . 4)
#'(1 1)
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)
the score builds without error and I get a PDF, but the beaming is
still the default - eg 32nd notes are beamed eight at a time.
Here's my short example. How do I get four beams per bar?
\version 2.13.29
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4) % time signature fraction
#'(1 . 4) % base moment fraction
#'(1 1)% beatStructure
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
\relative c'' {
\time 2/4
\changeBeaming
\repeat unfold 8 c16
\times 8/12 { \repeat unfold 12 c16 }
\repeat unfold 16 c32
\times 16/24 { \repeat unfold 24 c32 }
}
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
attachment
Re: Beam settings in 2.13.29
Hi Nick
You got the hard bit right, but from 2.13.29 you can
use the simpler
changeBeaming = \set beamExceptions =
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
to change the beaming exceptions.
Trevor
- Original Message -
From: Nick Payne nick.pa...@internode.on.net
To: lilypond-user lilypond-user@gnu.org
Sent: Thursday, August 05, 2010 1:22 AM
Subject: Beam settings in 2.13.29
In 2/4 time, in earlier versions I used
changeBeaming = \overrideBeamSettings #'Voice #'(2 . 4) #'end
#'((* . (2))
((1 . 8) . (2 2))
((1 . 16) . (2 2 2 2))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)))
to get 16th and 32nd notes and tupletted 16th 32nd notes grouped
as I wanted, putting \changeBeaming in the voice where it's
needed.
2.13.29 convert-ly tells me that I need to change this manually to
use overrideTimeSignatureSettings or beamExceptions, but I'm
struggling to find an example that I can use as a base.
I tried changing my override to:
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4)
#'(1 . 4)
#'(1 1)
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)
the score builds without error and I get a PDF, but the beaming is
still the default - eg 32nd notes are beamed eight at a time.
Here's my short example. How do I get four beams per bar?
\version 2.13.29
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4) % time signature fraction
#'(1 . 4) % base moment fraction
#'(1 1)% beatStructure
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
\relative c'' {
\time 2/4
\changeBeaming
\repeat unfold 8 c16
\times 8/12 { \repeat unfold 12 c16 }
\repeat unfold 16 c32
\times 16/24 { \repeat unfold 24 c32 }
}
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
Thanks, that works. I assume the command to revert beaming to the
defaults is \set beamExceptions = #'()
I'd still like to understand why what I did with
overrideTimeSignatureSettings didn't work. From my reading of s.1.2.3 of
the notation manual it should have.
Nick
On 05/08/10 18:02, Trevor Daniels wrote:
Hi Nick
You got the hard bit right, but from 2.13.29 you can
use the simpler
changeBeaming = \set beamExceptions =
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
to change the beaming exceptions.
Trevor
- Original Message - From: Nick Payne
nick.pa...@internode.on.net
To: lilypond-user lilypond-user@gnu.org
Sent: Thursday, August 05, 2010 1:22 AM
Subject: Beam settings in 2.13.29
In 2/4 time, in earlier versions I used
changeBeaming = \overrideBeamSettings #'Voice #'(2 . 4) #'end #'((* .
(2))
((1 . 8) . (2 2))
((1 . 16) . (2 2 2 2))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)))
to get 16th and 32nd notes and tupletted 16th 32nd notes grouped as I
wanted, putting \changeBeaming in the voice where it's needed.
2.13.29 convert-ly tells me that I need to change this manually to
use overrideTimeSignatureSettings or beamExceptions, but I'm
struggling to find an example that I can use as a base.
I tried changing my override to:
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4)
#'(1 . 4)
#'(1 1)
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)
the score builds without error and I get a PDF, but the beaming is
still the default - eg 32nd notes are beamed eight at a time.
Here's my short example. How do I get four beams per bar?
\version 2.13.29
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4) % time signature fraction
#'(1 . 4) % base moment fraction
#'(1 1)% beatStructure
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
\relative c'' {
\time 2/4
\changeBeaming
\repeat unfold 8 c16
\times 8/12 { \repeat unfold 12 c16 }
\repeat unfold 16 c32
\times 16/24 { \repeat unfold 24 c32 }
}
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Beam settings in 2.13.29
In 2/4 time, in earlier versions I used
changeBeaming = \overrideBeamSettings #'Voice #'(2 . 4) #'end #'((* . (2))
((1 . 8) . (2 2))
((1 . 16) . (2 2 2 2))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)))
to get 16th and 32nd notes and tupletted 16th 32nd notes grouped as I
wanted, putting \changeBeaming in the voice where it's needed.
2.13.29 convert-ly tells me that I need to change this manually to use
overrideTimeSignatureSettings or beamExceptions, but I'm struggling to
find an example that I can use as a base.
I tried changing my override to:
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4)
#'(1 . 4)
#'(1 1)
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)
the score builds without error and I get a PDF, but the beaming is still
the default - eg 32nd notes are beamed eight at a time.
Here's my short example. How do I get four beams per bar?
\version 2.13.29
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4) % time signature fraction
#'(1 . 4) % base moment fraction
#'(1 1)% beatStructure
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
\relative c'' {
\time 2/4
\changeBeaming
\repeat unfold 8 c16
\times 8/12 { \repeat unfold 12 c16 }
\repeat unfold 16 c32
\times 16/24 { \repeat unfold 24 c32 }
}
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
p.s. The search function in the 2.13 online doc searches the wrong
version. If I go to the 2.13.29 notation reference at
http://lilypond.org/doc/v2.13/Documentation/notation/ and enter
overrideTimeSignatureSettings in the search box at the bottom of the
left pane, nothing is found because the search is against the 2.12 doc.
The returned Google search term is:
site:lilypond.org +v2.12 overrideTimeSignatureSettings
Mind you, substituting 2.13 in the search doesn't find anything either.
I guess it hasn't been indexed yet. I had to go to the index at
http://lilypond.org/doc/v2.13/Documentation/notation/lilypond-command-index
to find \overrideTimeSignatureSettings.
Nick
On 05/08/10 10:22, Nick Payne wrote:
In 2/4 time, in earlier versions I used
changeBeaming = \overrideBeamSettings #'Voice #'(2 . 4) #'end #'((* .
(2))
((1 . 8) . (2 2))
((1 . 16) . (2 2 2 2))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)))
to get 16th and 32nd notes and tupletted 16th 32nd notes grouped as I
wanted, putting \changeBeaming in the voice where it's needed.
2.13.29 convert-ly tells me that I need to change this manually to use
overrideTimeSignatureSettings or beamExceptions, but I'm struggling to
find an example that I can use as a base.
I tried changing my override to:
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4)
#'(1 . 4)
#'(1 1)
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6)
the score builds without error and I get a PDF, but the beaming is
still the default - eg 32nd notes are beamed eight at a time.
Here's my short example. How do I get four beams per bar?
\version 2.13.29
changeBeaming = \overrideTimeSignatureSettings
#'Voice
#'(2 . 4) % time signature fraction
#'(1 . 4) % base moment fraction
#'(1 1)% beatStructure
#'((end . (((1 . 16) . (2 2 2 2))
((1 . 24) . (3 3 3 3))
((1 . 32) . (4 4 4 4))
((1 . 48) . (6 6 6 6) % beamExceptions
\relative c'' {
\time 2/4
\changeBeaming
\repeat unfold 8 c16
\times 8/12 { \repeat unfold 12 c16 }
\repeat unfold 16 c32
\times 16/24 { \repeat unfold 24 c32 }
}
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings in 2.13.29
On Thu, Aug 5, 2010 at 1:30 AM, Nick Payne nick.pa...@internode.on.net wrote: p.s. The search function in the 2.13 online doc searches the wrong version. p.s. http://code.google.com/p/lilypond/issues/detail?id=1171 - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Creating Automatic Beam Settings in Irregular Meters
Hello, I am notating a piece of music that is in 11/8. I've been trying to figure out how I can get Lilypond to automatically group beams in a 3 +3+2+3 pattern. I tried the override-auto-beam-setting command, but it didn't work, I'm assuming it's because there is no auto-beam setting in the first place for 11/8. I also tried \set beatGrouping = #' (3 3 2 3), also to no success. In both attempts, the compiler still parsed it, except in neither did it have any effect. My Lilypond is version 2.10.25. Can anybody help me? Thank you, Dix ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Creating Automatic Beam Settings in Irregular Meters
Dix Franke wrote Monday, March 01, 2010 2:49 PM I am notating a piece of music that is in 11/8. I've been trying to figure out how I can get Lilypond to automatically group beams in a 3 +3+2+3 pattern. I tried the override-auto-beam-setting command, but it didn't work, I'm assuming it's because there is no auto-beam setting in the first place for 11/8. No, this would not be the reason. It's actually easier if there is no auto-beam setting already defined, otherwise it would need to be cancelled first. But it can be tricky to get the commands' syntax right. Be sure you are using the manuals for the version of LP you are using, as there have been several changes to the auto-beam setting commands since 2.10. The settings you need should be somthing like #(override-auto-beam-setting '(end 1 8 11 8) 3 8) #(override-auto-beam-setting '(end 1 8 11 8) 6 8) #(override-auto-beam-setting '(end 1 8 11 8) 8 8) to beam eighth notes as you want them I also tried \set beatGrouping = #' (3 3 2 3), also to no success. I don't think this worked in 2.10. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Creating Automatic Beam Settings in Irregular Meters
On 1 Mar 2010, at 15:49, Dix Franke wrote: I am notating a piece of music that is in 11/8. I've been trying to figure out how I can get Lilypond to automatically group beams in a 3+3+2+3 pattern. I tried the override-auto-beam-setting command, but it didn't work, I'm assuming it's because there is no auto-beam setting in the first place for 11/8. I also tried \set beatGrouping = #' (3 3 2 3), also to no success. In both attempts, the compiler still parsed it, except in neither did it have any effect. My Lilypond is version 2.10.25. Can anybody help me? This has been changed, it seems. In 2.13.7 I use for example: \time 12/16 \overrideBeamSettings #'Score #'(12 . 16) #'end #'((* . (3 2 2 3 2))) which in your case should be: \time 11/8 \overrideBeamSettings #'Score #'(11 . 8) #'end #'((* . (3 3 2 3))) Hans ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: where is the default auto-beam settings for 2/4 defined?
Frédéric Bron wrote Wednesday, September 02, 2009 6:18 AM Your remark is interesting! The doc says if they are some rules defined in auto-beam.scm, you MUST use #(override and #(revert... But only when the beam durations are the same. This is stated, maybe not very clearly, where I've indicated, here: There are two mutually exclusive ways in which these rules may be modified. The first, modifying the grouping of beats, applies to uncommon time signatures, i.e. those for which there are no predefined rules defining the beam end points. The second method, modifying the specification of the beam end points, can be used for any time signature. This second method must be used for those time signatures and beam durations combinations for which beam ending rules are ^^ pre-defined, unless these have all been reverted. There are predefined rules for time signatures of 3/2, 3/4, 4/4, 2/4, 4/8, 4/16, 6/8, 9/8 and 12/8. That's why the rules for 32nd notes don't affect 8th note beaming. Also see the comment in scm/auto-beam.scm just above this entry. This was very unsatisfactory, but auto-beaming has changed completely in 2.13, so the issue has already been addressed. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
where is the default auto-beam settings for 2/4 defined?
In the following example, beams for 8 notes end at 1:4, 2:4, 3:4 and 4:4
but the only thing I can find in scm/auto-beam.scm about time 2/4 is:
((end 1 32 2 4) . ,(ly:make-moment 1 8))
((end 1 32 2 4) . ,(ly:make-moment 2 8))
((end 1 32 2 4) . ,(ly:make-moment 3 8))
How can I revert this rule to make 8 notes grouped by measure?
\version 2.12.2
{ \time 2/4
#(revert-auto-beam-setting '(end 1 8 2 4) 1 4) % does not work
\repeat unfold 16 { c'8 }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: where is the default auto-beam settings for 2/4 defined?
Frédéric Bron wrote Tuesday, September 01, 2009 9:37 PM
In the following example, beams for 8 notes end at 1:4, 2:4, 3:4
and 4:4
but the only thing I can find in scm/auto-beam.scm about time 2/4
is:
((end 1 32 2 4) . ,(ly:make-moment 1 8))
((end 1 32 2 4) . ,(ly:make-moment 2 8))
((end 1 32 2 4) . ,(ly:make-moment 3 8))
How can I revert this rule to make 8 notes grouped by measure?
\version 2.12.2
{ \time 2/4
#(revert-auto-beam-setting '(end 1 8 2 4) 1 4) % does not work
\repeat unfold 16 { c'8 }
}
I don't have the exact 2.12.2 version to hand,
but if scm/auto-beam.scm is as you say there
is no need to revert these settings as they
only affect 32nd notes. All you need to do is
to change the default beat-grouping:
\set beatGrouping = #'(2)
In version 2.12.1 (which I have to hand) there
is also a rule which affects all beams. This
will need reverting if it exists in 2.12.2 with
#(revert-auto-beam-setting '(end * * 2 4) 1 4)
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: where is the default auto-beam settings for 2/4 defined?
I don't have the exact 2.12.2 version to hand, but if scm/auto-beam.scm is as you say there is no need to revert these settings as they only affect 32nd notes. All you need to do is to change the default beat-grouping: \set beatGrouping = #'(2) In version 2.12.1 (which I have to hand) there is also a rule which affects all beams. This will need reverting if it exists in 2.12.2 with #(revert-auto-beam-setting '(end * * 2 4) 1 4) I confirm that the rule #(revert-auto-beam-setting '(end * * 2 4) 1 4) disappeared from 2.12.2 Your remark is interesting! The doc says if they are some rules defined in auto-beam.scm, you MUST use #(override and #(revert... But it seams we can mix the 2 methods... extract of the doc in NR/1.2.4 Beams/Setting automatic beam behavior: There are two mutually exclusive ways in which these rules may be modified. The first, modifying the grouping of beats, applies to uncommon time signatures, i.e. those for which there are no predefined rules defining the beam end points. The second method, modifying the specification of the beam end points, can be used for any time signature. This second method must be used for those time signatures and beam durations combinations for which beam ending rules are pre-defined, unless these have all been reverted. There are predefined rules for time signatures of 3/2, 3/4, 4/4, 2/4, 4/8, 4/16, 6/8, 9/8 and 12/8. Frédéric --- Frédéric Bron (frederic.b...@m4x.org) Villa des Quatre Chemins, Centre Hospitalier, BP 208 38506 VOIRON CEDEX tél. : (33) 4 76 67 17 27 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam-settings for triplets and sixtuplets
Stefan
The default behaviour is to end 1/8 triplets at 1/4 beats in 4 4 time.
So to beam sextuplets you need to revert the default beaming rules
which end 1/12 notes at the 1/4 and 3/4 beats.
The relevant default rules are (see scm/auto-beam.scm):
((end * * 4 4) . ,(ly:make-moment 1 2))
((end 1 12 4 4) . ,(ly:make-moment 1 4))
((end 1 12 4 4) . ,(ly:make-moment 3 4))
so I think this will do what you wanted:
AT = #(define-music-function (parser location x) (ly:music?)
#{
% #(override-auto-beam-setting '(end 1 12 * *) 1 4 'Staff)
% #(override-auto-beam-setting '(end 1 12 * *) 2 4 'Staff)
% #(override-auto-beam-setting '(end 1 12 * *) 3 4 'Staff)
\set tupletSpannerDuration = #(ly:make-moment 1 4 )
\times 2/3 { $x } \unset tupletSpannerDuration
#(revert-auto-beam-setting '(end 1 12 4 4) 1 4 'Staff)
% #(revert-auto-beam-setting '(end 1 12 * *) 2 4 'Staff)
#(revert-auto-beam-setting '(end 1 12 4 4) 3 4 'Staff)
#})
Trevor
- Original Message -
From: Stefan Thomas kontrapunktste...@googlemail.com
To: lilypond-user lilypond-user@gnu.org
Sent: Monday, January 05, 2009 3:06 PM
Subject: beam-settings for triplets and sixtuplets
Dear Lilypond-users,
in the following snippet I changed succesfully the beam-settings for
8th-triplet.
But I couldn't revert it, for the sixputplets.
Here the example:
\version 2.12.0
AT = #(define-music-function (parser location x) (ly:music?)
#{
#(override-auto-beam-setting '(end 1 12 * *) 1 4 'Staff)
#(override-auto-beam-setting '(end 1 12 * *) 2 4 'Staff)
#(override-auto-beam-setting '(end 1 12 * *) 3 4 'Staff)
\set tupletSpannerDuration = #(ly:make-moment 1 4 )
\times 2/3 { $x } \unset tupletSpannerDuration
#(revert-auto-beam-setting '(end 1 12 * *) 1 4 'Staff)
#(revert-auto-beam-setting '(end 1 12 * *) 2 4 'Staff)
#(revert-auto-beam-setting '(end 1 12 * *) 3 4 'Staff)
#})
\new Staff \relative { \time 4/4\AT { d 8 e f g f e f e d f e d}
%the beams behave like expected
\times 4/6 { c8 d e f e d } \times 4/6 { e f g a g f} %the beams,
unfortunatley, don't behave like expected
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
beam-settings for triplets and sixtuplets
Dear Lilypond-users,
in the following snippet I changed succesfully the beam-settings for
8th-triplet.
But I couldn't revert it, for the sixputplets.
Here the example:
\version 2.12.0
AT = #(define-music-function (parser location x) (ly:music?)
#{
#(override-auto-beam-setting '(end 1 12 * *) 1 4 'Staff)
#(override-auto-beam-setting '(end 1 12 * *) 2 4 'Staff)
#(override-auto-beam-setting '(end 1 12 * *) 3 4 'Staff)
\set tupletSpannerDuration = #(ly:make-moment 1 4 )
\times 2/3 { $x } \unset tupletSpannerDuration
#(revert-auto-beam-setting '(end 1 12 * *) 1 4 'Staff)
#(revert-auto-beam-setting '(end 1 12 * *) 2 4 'Staff)
#(revert-auto-beam-setting '(end 1 12 * *) 3 4 'Staff)
#})
\new Staff \relative { \time 4/4\AT { d 8 e f g f e f e d f e d}
%the beams behave like expected
\times 4/6 { c8 d e f e d } \times 4/6 { e f g a g f} %the beams,
unfortunatley, don't behave like expected
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam-settings for triplets and sixtuplets
Dear Trevor,
thanks for Your advice! It works now!
2009/1/5 Trevor Daniels t.dani...@treda.co.uk:
Stefan
The default behaviour is to end 1/8 triplets at 1/4 beats in 4 4 time.
So to beam sextuplets you need to revert the default beaming rules
which end 1/12 notes at the 1/4 and 3/4 beats.
The relevant default rules are (see scm/auto-beam.scm):
((end * * 4 4) . ,(ly:make-moment 1 2))
((end 1 12 4 4) . ,(ly:make-moment 1 4))
((end 1 12 4 4) . ,(ly:make-moment 3 4))
so I think this will do what you wanted:
AT = #(define-music-function (parser location x) (ly:music?)
#{
% #(override-auto-beam-setting '(end 1 12 * *) 1 4 'Staff)
% #(override-auto-beam-setting '(end 1 12 * *) 2 4 'Staff)
% #(override-auto-beam-setting '(end 1 12 * *) 3 4 'Staff)
\set tupletSpannerDuration = #(ly:make-moment 1 4 )
\times 2/3 { $x } \unset tupletSpannerDuration
#(revert-auto-beam-setting '(end 1 12 4 4) 1 4 'Staff)
% #(revert-auto-beam-setting '(end 1 12 * *) 2 4 'Staff)
#(revert-auto-beam-setting '(end 1 12 4 4) 3 4 'Staff)
#})
Trevor
- Original Message - From: Stefan Thomas
kontrapunktste...@googlemail.com
To: lilypond-user lilypond-user@gnu.org
Sent: Monday, January 05, 2009 3:06 PM
Subject: beam-settings for triplets and sixtuplets
Dear Lilypond-users,
in the following snippet I changed succesfully the beam-settings for
8th-triplet.
But I couldn't revert it, for the sixputplets.
Here the example:
\version 2.12.0
AT = #(define-music-function (parser location x) (ly:music?)
#{
#(override-auto-beam-setting '(end 1 12 * *) 1 4 'Staff)
#(override-auto-beam-setting '(end 1 12 * *) 2 4 'Staff)
#(override-auto-beam-setting '(end 1 12 * *) 3 4 'Staff)
\set tupletSpannerDuration = #(ly:make-moment 1 4 )
\times 2/3 { $x } \unset tupletSpannerDuration
#(revert-auto-beam-setting '(end 1 12 * *) 1 4 'Staff)
#(revert-auto-beam-setting '(end 1 12 * *) 2 4 'Staff)
#(revert-auto-beam-setting '(end 1 12 * *) 3 4 'Staff)
#})
\new Staff \relative { \time 4/4\AT { d 8 e f g f e f e d f e d}
%the beams behave like expected
\times 4/6 { c8 d e f e d } \times 4/6 { e f g a g f} %the beams,
unfortunatley, don't behave like expected
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
Carl D. Sorensen wrote Thursday, December 25, 2008 12:21 AM
On 12/24/08 3:31 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
Herbert Liechti wrote Tuesday, December 23, 2008 6:40 AM
Neil Puttock schrieb:
2008/12/22 Trevor Daniels t.dani...@treda.co.uk:
Reinhold Kainhofer wrote Monday, December 22, 2008 4:22 PM
He sent me the whole file and the culprit is a PianoStaff, which
seems
to
somehow override the score's beamGrouping. So, one cannot use
\set Score.beatGrouping = #'(1 1 1 1 1 1)
but rather has to use
\set Staff.beatGrouping = #'(1 1 1 1 1 1)
Then the beaming also works fine for staves inside a PianoStaff.
Hmm. Does that mean that context properties set at the Score
level are inherited by the Staff context only if there is no
interposed staff grouping?
I've never noticed this to be the case; I think we need to see
Herbert's file to work out whether there's something else that's
influencing this behaviour.
I'm attaching the file. I already changed the beatGrouping from
Score to Staff context.
I've tracked down the problem here. It is nothing to to do with the
PianoStaff. It is due to placing a second \time command in the lower
staff. Here's an extract from the score which shows the problem
clearly. Uncomment the second \time command and the
beamGrouping override in the Score context fails in both staves.
Specify \time in only one staff and it works fine in both staves.
\score {
\new Staff {
\time 6/8
\set Score.beatGrouping = #'(1 1 1 1 1 1)
\repeat unfold 6 { \times 2/3 { bes16 as es } }
}
\new Staff {
% \time 6/8
\repeat unfold 6 { \times 2/3 { bes16 as es } }
}
Aha! This makes sense. This is because time 6/8 sets beatGrouping to (3
3). And beatGrouping doesn't live on the Staff level.
This probably becomes a documentation bug.
OK. I'll fix the docs.
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
Herbert Liechti wrote Tuesday, December 23, 2008 6:40 AM
Neil Puttock schrieb:
2008/12/22 Trevor Daniels t.dani...@treda.co.uk:
Reinhold Kainhofer wrote Monday, December 22, 2008 4:22 PM
He sent me the whole file and the culprit is a PianoStaff, which seems
to
somehow override the score's beamGrouping. So, one cannot use
\set Score.beatGrouping = #'(1 1 1 1 1 1)
but rather has to use
\set Staff.beatGrouping = #'(1 1 1 1 1 1)
Then the beaming also works fine for staves inside a PianoStaff.
Hmm. Does that mean that context properties set at the Score
level are inherited by the Staff context only if there is no
interposed staff grouping?
I've never noticed this to be the case; I think we need to see
Herbert's file to work out whether there's something else that's
influencing this behaviour.
I'm attaching the file. I already changed the beatGrouping from
Score to Staff context.
I've tracked down the problem here. It is nothing to to do with the
PianoStaff. It is due to placing a second \time command in the lower
staff. Here's an extract from the score which shows the problem
clearly. Uncomment the second \time command and the
beamGrouping override in the Score context fails in both staves.
Specify \time in only one staff and it works fine in both staves.
\score {
\new Staff {
\time 6/8
\set Score.beatGrouping = #'(1 1 1 1 1 1)
\repeat unfold 6 { \times 2/3 { bes16 as es } }
}
\new Staff {
% \time 6/8
\repeat unfold 6 { \times 2/3 { bes16 as es } }
}
}
Copied to bug-lily for further comment there.
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
On 12/24/08 3:31 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
Herbert Liechti wrote Tuesday, December 23, 2008 6:40 AM
Neil Puttock schrieb:
2008/12/22 Trevor Daniels t.dani...@treda.co.uk:
Reinhold Kainhofer wrote Monday, December 22, 2008 4:22 PM
He sent me the whole file and the culprit is a PianoStaff, which seems
to
somehow override the score's beamGrouping. So, one cannot use
\set Score.beatGrouping = #'(1 1 1 1 1 1)
but rather has to use
\set Staff.beatGrouping = #'(1 1 1 1 1 1)
Then the beaming also works fine for staves inside a PianoStaff.
Hmm. Does that mean that context properties set at the Score
level are inherited by the Staff context only if there is no
interposed staff grouping?
I've never noticed this to be the case; I think we need to see
Herbert's file to work out whether there's something else that's
influencing this behaviour.
I'm attaching the file. I already changed the beatGrouping from
Score to Staff context.
I've tracked down the problem here. It is nothing to to do with the
PianoStaff. It is due to placing a second \time command in the lower
staff. Here's an extract from the score which shows the problem
clearly. Uncomment the second \time command and the
beamGrouping override in the Score context fails in both staves.
Specify \time in only one staff and it works fine in both staves.
\score {
\new Staff {
\time 6/8
\set Score.beatGrouping = #'(1 1 1 1 1 1)
\repeat unfold 6 { \times 2/3 { bes16 as es } }
}
\new Staff {
% \time 6/8
\repeat unfold 6 { \times 2/3 { bes16 as es } }
}
Aha! This makes sense. This is because time 6/8 sets beatGrouping to (3
3). And beatGrouping doesn't live on the Staff level.
This probably becomes a documentation bug.
Carl
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
On Mon, Dec 22, 2008 at 08:19:27AM +0100, Herbert Liechti wrote:
I tried several settings without success:
You were close.
{
\repeat volta 2 {
\time 6/8
\set Score.beatGrouping = #'(3 3 3 3 3 3)
\repeat unfold 6 { \times 2/3 { bes16 g es } } |
\repeat unfold 6 { \times 2/3 { bes16 as es } } |
}
}
An other question: Is it possible to achieve the same
behavior in the \times 2/3 part, so that the 3 symbol for triplets
is engraved only once?
There's a property that's something like tupletPrintNumber. Go to
the NR page for triplets, follow the IR link, and take a look at
the tweakable properties.
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
Graham Percival schrieb:
On Mon, Dec 22, 2008 at 08:19:27AM +0100, Herbert Liechti wrote:
I tried several settings without success:
You were close.
{
\repeat volta 2 {
\time 6/8
\set Score.beatGrouping = #'(3 3 3 3 3 3)
\repeat unfold 6 { \times 2/3 { bes16 g es } } |
\repeat unfold 6 { \times 2/3 { bes16 as es } } |
}
}
I tried this before but it is not working (version 2.11.63). I found
this solution
\repeat volta 2 {
\set Score.beatGrouping = #'(3 3 3 3 3 3)
\times 2/3 { bes16[ g es] }
\override TupletNumber #'stencil = ##f
\repeat unfold 5 { \times 2/3 { bes16[ g es] } } |
\repeat unfold 6 { \times 2/3 { bes16[ as es] } } |
}
Seems that the brackets are required for achieving the
desired behavior.
Thank you and best regards
Herbie
--
herbert.liec...@thinx.ch, ThinX AG, Poststrasse 2, CH-4500 Solothurn
Tel +41 (0)32 623 81 66, Mobile +41 (0)76 334 81 66, http://www.thinx.ch
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
Reinhold Kainhofer wrote: \set Score.beatGrouping = #'(1 1 1 1 1 1) This is way easier than using several lines like: #(override-auto-beam-setting '(end * * 6 8) 1 8) or similar. Also if you need to switch the tuplet numbers on and off a lot, you could make a shorthand for it, like numberOff = \override TupletNumber #'stencil = ##f numberOn = \revert TupletNumber #'stencil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 22. Dezember 2008 09:04:12 schrieb Graham Percival:
You were close.
{
\repeat volta 2 {
\time 6/8
\set Score.beatGrouping = #'(3 3 3 3 3 3)
That's close, too, but not correct ;-)
Am Montag, 22. Dezember 2008 09:55:25 schrieb Herbert Liechti:
\repeat volta 2 {
\set Score.beatGrouping = #'(3 3 3 3 3 3)
\times 2/3 { bes16[ g es] }
\override TupletNumber #'stencil = ##f
\repeat unfold 5 { \times 2/3 { bes16[ g es] } } |
\repeat unfold 6 { \times 2/3 { bes16[ as es] } } |
}
You're almost there...
Seems that the brackets are required for achieving the
desired behavior.
Actually, no. What is needed is a correct value for the beatGrouping ;-) You
don't want 3 eighth notes to be beamed together, do you? You want the beams to
be broken after EACH eighth note. So the correct value is to set beat Grouping
to #'(1 1 1 1 1 1 ), which tells lilypond to beam together all subdivisions of
an eighth note, but don't beam across eighth note boundaries.
So, your complete example would be:
\transpose c c'' {
\clef treble
\time 6/8
\repeat volta 2 {
\set Score.beatGrouping = #'(1 1 1 1 1 1)
\times 2/3 { bes16 g es }
\override TupletNumber #'stencil = ##f
\repeat unfold 5 { \times 2/3 { bes16 g es } } |
\repeat unfold 6 { \times 2/3 { bes16 as es } } |
}
}
Cheers,
Reinhold
- --
- --
Reinhold Kainhofer, Vienna University of Technology, Austria
email: reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
* K Desktop Environment, http://www.kde.org, KOrganizer maintainer
* Chorvereinigung Jung-Wien, http://www.jung-wien.at/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQFJT4ALTqjEwhXvPN0RAg9LAKC+iAeaG/hipcibnyMkZLpe9GQ+fwCfaDWc
Ym3ObXiJf4TtRjxKIOuWsWU=
=ehrY
-END PGP SIGNATURE-
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
On Mon, Dec 22, 2008 at 12:54:50PM +0100, Reinhold Kainhofer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 22. Dezember 2008 09:04:12 schrieb Graham Percival:
You were close.
{
\repeat volta 2 {
\time 6/8
\set Score.beatGrouping = #'(3 3 3 3 3 3)
That's close, too, but not correct ;-)
I must be getting old. What's the difference between my example
in 2.11.65 and the picture? Octave, key signature, and tempo
marking, but I could have sworn that the beaming was the same.
Actually, no. What is needed is a correct value for the
beatGrouping ;-) You don't want 3 eighth notes to be beamed
together, do you? You want the beams to be broken after EACH
eighth note. So the correct value is to set beat Grouping to
#'(1 1 1 1 1 1 ), which tells lilypond to beam together all
subdivisions of an eighth note, but don't beam across eighth
note boundaries.
I must admit that this makes sense. Am I seeing a bug in .65 that
was fixed in .66? Because the #'(3 3 3 3 3 3) certainly seems to
work here...
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 22. Dezember 2008 13:49:10 schrieb Graham Percival:
On Mon, Dec 22, 2008 at 12:54:50PM +0100, Reinhold Kainhofer wrote:
Am Montag, 22. Dezember 2008 09:04:12 schrieb Graham Percival:
You were close.
{
\repeat volta 2 {
\time 6/8
\set Score.beatGrouping = #'(3 3 3 3 3 3)
That's close, too, but not correct ;-)
I must be getting old. What's the difference between my example
in 2.11.65 and the picture? Octave, key signature, and tempo
marking, but I could have sworn that the beaming was the same.
Yes, the beaming is the same, but that's not due to your beatGrouping value,
but due to the internal workings: Your beatGrouping value is inconsistent (it
defines a rule for 18 eighth notes in a measure, which contradicts the time
signature, so lilypond does not use the beatGrouping value at all and resolves
to beaming each beat separately).
You can try it also with other values, which don't make sense. For example,
\set Score.beatGrouping = #'(17 3 1)
will give you the same beat-wise grouping.
On the other hand, once you shorten your list to the correct measure length
\set Score.beatGrouping = #'(3 3)
then the beaming will not be triplet-wise, but the first three triplets will
be beamed together.
I must admit that this makes sense. Am I seeing a bug in .65 that
was fixed in .66? Because the #'(3 3 3 3 3 3) certainly seems to
work here...
As exaplained above, setting beatGrouping to this value effectively causes
LilyPond to ignore that setting at all. It has the same effect as using
\uset Score.beatGrouping
In this case, LilyPond will fall back to beat-wise grouping (which is
coincidentally what is desired in this case, but that's pure luck ;-) )
Cheers,
Reinhold
- --
- --
Reinhold Kainhofer, Vienna University of Technology, Austria
email: reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
* K Desktop Environment, http://www.kde.org, KOrganizer maintainer
* Chorvereinigung Jung-Wien, http://www.jung-wien.at/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQFJT5a+TqjEwhXvPN0RAq2pAKDIXzAjrXEE5LJQ/v4pFBRNvWmCtACeIBzC
yn1UMJ8Tkl+RmgxBxdI5n98=
=GYEv
-END PGP SIGNATURE-
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
Reinhold Kainhofer schrieb:
You're almost there...
Seems that the brackets are required for achieving the
desired behavior.
Actually, no. What is needed is a correct value for the beatGrouping
;-) You
don't want 3 eighth notes to be beamed together, do you? You want the
beams to
be broken after EACH eighth note. So the correct value is to set beat
Grouping
to #'(1 1 1 1 1 1 ), which tells lilypond to beam together all
subdivisions of
an eighth note, but don't beam across eighth note boundaries.
So, your complete example would be:
\transpose c c'' {
\clef treble
\time 6/8
\repeat volta 2 {
\set Score.beatGrouping = #'(1 1 1 1 1 1)
\times 2/3 { bes16 g es }
\override TupletNumber #'stencil = ##f
\repeat unfold 5 { \times 2/3 { bes16 g es } } |
\repeat unfold 6 { \times 2/3 { bes16 as es } } |
}
}
Reinhold
I tried this code but it is not working even after upgrading
to version 2.11.65. Resulting picture is
dingsbums
best regards
Herbie
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
Reinhold Kainhofer schrieb:
You're almost there...
Seems that the brackets are required for achieving the
desired behavior.
Actually, no. What is needed is a correct value for the beatGrouping
;-) You
don't want 3 eighth notes to be beamed together, do you? You want the
beams to
be broken after EACH eighth note. So the correct value is to set beat
Grouping
to #'(1 1 1 1 1 1 ), which tells lilypond to beam together all
subdivisions of
an eighth note, but don't beam across eighth note boundaries.
So, your complete example would be:
\transpose c c'' {
\clef treble
\time 6/8
\repeat volta 2 {
\set Score.beatGrouping = #'(1 1 1 1 1 1)
\times 2/3 { bes16 g es }
\override TupletNumber #'stencil = ##f
\repeat unfold 5 { \times 2/3 { bes16 g es } } |
\repeat unfold 6 { \times 2/3 { bes16 as es } } |
}
}
Cheers,
Reinhold
Reinhold
I tried this code but it is not working even after upgrading
to version 2.11.65. Resulting picture is
best regards
Herbie
PS sorry once again, picture was missed in the last post ;-)
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
Herbert Liechti wrote Re: beam settings
Reinhold Kainhofer schrieb:
You're almost there...
Seems that the brackets are required for achieving the
desired behavior.
Actually, no. What is needed is a correct value for the beatGrouping
;-) You
don't want 3 eighth notes to be beamed together, do you? You want the
beams to
be broken after EACH eighth note. So the correct value is to set beat
Grouping
to #'(1 1 1 1 1 1 ), which tells lilypond to beam together all
subdivisions of
an eighth note, but don't beam across eighth note boundaries.
So, your complete example would be:
\transpose c c'' {
\clef treble
\time 6/8
\repeat volta 2 {
\set Score.beatGrouping = #'(1 1 1 1 1 1)
\times 2/3 { bes16 g es }
\override TupletNumber #'stencil = ##f
\repeat unfold 5 { \times 2/3 { bes16 g es } } |
\repeat unfold 6 { \times 2/3 { bes16 as es } } |
}
}
Cheers,
Reinhold
Reinhold
I tried this code but it is not working even after upgrading
to version 2.11.65. Resulting picture is
dings
Reinhold's short example works here, but I see from your
attached jpg that you've incorporated it in some more
extensive code. Perhaps if you post that code on the list
we could see what has gone wrong.
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 22. Dezember 2008 schrieb Trevor Daniels: Reinhold's short example works here, but I see from your attached jpg that you've incorporated it in some more extensive code. He sent me the whole file and the culprit is a PianoStaff, which seems to somehow override the score's beamGrouping. So, one cannot use \set Score.beatGrouping = #'(1 1 1 1 1 1) but rather has to use \set Staff.beatGrouping = #'(1 1 1 1 1 1) Then the beaming also works fine for staves inside a PianoStaff. Cheers, Reinhold - -- - -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJT77iTqjEwhXvPN0RAhSAAKCKBLXAr723vfsn7BWENvZR6s2OMwCg27Rk 9vB0T5n8YK53giyFZHddsrA= =N2Kn -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
Reinhold Kainhofer wrote Monday, December 22, 2008 4:22 PM Am Montag, 22. Dezember 2008 schrieb Trevor Daniels: Reinhold's short example works here, but I see from your attached jpg that you've incorporated it in some more extensive code. He sent me the whole file and the culprit is a PianoStaff, which seems to somehow override the score's beamGrouping. So, one cannot use \set Score.beatGrouping = #'(1 1 1 1 1 1) but rather has to use \set Staff.beatGrouping = #'(1 1 1 1 1 1) Then the beaming also works fine for staves inside a PianoStaff. Hmm. Does that mean that context properties set at the Score level are inherited by the Staff context only if there is no interposed staff grouping? (Copied to -devel for comment) Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
Reinhold Kainhofer schrieb: Am Montag, 22. Dezember 2008 schrieb Trevor Daniels: Reinhold's short example works here, but I see from your attached jpg that you've incorporated it in some more extensive code. He sent me the whole file and the culprit is a PianoStaff, which seems to somehow override the score's beamGrouping. So, one cannot use \set Score.beatGrouping = #'(1 1 1 1 1 1) but rather has to use \set Staff.beatGrouping = #'(1 1 1 1 1 1) Then the beaming also works fine for staves inside a PianoStaff. Yes, that is working. Thank you very much for your patient and for helping. Perhaps a good example for the documentation which points out the behavior of the beatGrouping in a clear way with the explanation of Reinhold Kainhofer in the earlier post in this threat. Best regards Herbert ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beam settings
2008/12/22 Trevor Daniels t.dani...@treda.co.uk: Reinhold Kainhofer wrote Monday, December 22, 2008 4:22 PM He sent me the whole file and the culprit is a PianoStaff, which seems to somehow override the score's beamGrouping. So, one cannot use \set Score.beatGrouping = #'(1 1 1 1 1 1) but rather has to use \set Staff.beatGrouping = #'(1 1 1 1 1 1) Then the beaming also works fine for staves inside a PianoStaff. Hmm. Does that mean that context properties set at the Score level are inherited by the Staff context only if there is no interposed staff grouping? I've never noticed this to be the case; I think we need to see Herbert's file to work out whether there's something else that's influencing this behaviour. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
beam settings
Hello
I have some troubles to group beams like the following
picture:
I tried several settings without success:
oben = \transpose c c'' {
\clef treble
\global
%%\set beatLength = #(ly:make-moment 1 8)
\repeat volta 2 {
%\set subdivideBeams = ##t
%\set Score.beatLength = #(ly:make-moment 1 18)
%\set Score.beatGrouping = #'(3 3 3 3 3 3)
%%#(set-time-signature 18 16 '(3 3 3 3 3 3))
#(override-auto-beam-setting '(end * * 18 18) 3 18)
#(override-auto-beam-setting '(end * * 18 18) 6 18)
#(override-auto-beam-setting '(end * * 18 18) 9 18)
#(override-auto-beam-setting '(end * * 18 18) 12 18)
#(override-auto-beam-setting '(end * * 18 18) 15 18)
#(override-auto-beam-setting '(end * * 18 18) 18 18)
\repeat unfold 6 { \times 2/3 { bes16 g es } } |
\repeat unfold 6 { \times 2/3 { bes16 as es } } |
}
}
An other question: Is it possible to achieve the same
behavior in the \times 2/3 part, so that the 3 symbol for triplets
is engraved only once?
Thank you for helping
Best regards Herbert
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Beam settings
I have a problem with beams in Lilypond 1.5.59. Consider this file:
--
\score {
\notes \relative g'' {
\time 6/8
g8 g, g' a a, a' | b b, b' c c, c'
}
}
--
Lilypond 1.5.60 creates a good-looking score, but Lilypond 1.5.59 (which
is installed on my home computer) does not draw very well the first two
beams [g8 g, g'] and [a a, a']. I tried to change `staff-position' in
Voice.Beam:
--
\property Voice.Beam \set #'staff-position = #-10
--
But this line has no effect! I can put -2, -4, -10 or whatever else, and
the beams are still the same. Am I using the wrong property? In fact, I
looked on a old Lilypond 1.4.7 manual, since I am not able to compile the
1.5.x documentation.
Thanks
Maurizio
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Beam settings
I have a problem with beams in Lilypond 1.5.59. Consider this file:
--
\score {
\notes \relative g'' {
\time 6/8
g8 g, g' a a, a' | b b, b' c c, c'
}
}
--
Lilypond 1.5.60 creates a good-looking score, but Lilypond 1.5.59 (which
is installed on my home computer) does not draw very well the first two
beams [g8 g, g'] and [a a, a'].
I guess this was one of the bugs that was solved in 1.5.60.
I tried to change `staff-position' in
Voice.Beam:
--
\property Voice.Beam \set #'staff-position = #-10
--
But this line has no effect! I can put -2, -4, -10 or whatever else, and
the beams are still the same. Am I using the wrong property? In fact, I
looked on a old Lilypond 1.4.7 manual, since I am not able to compile the
1.5.x documentation.
I mostly use the on-line documentation for the latest 1.5.xx at
http://lilypond.org/development/
If you click on Documentation: Other..., you can find both
.ps.gz and .pdf versions of the manual, in addition to the
html.
/Mats
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
