On 12/15/10 5:49 PM, "Graham Percival" 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
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 is
On 12/15/10 3:43 PM, "Neil Puttock" wrote:
> On 10 August 2010 01:08, Carl Sorensen wrote:
>> On 8/9/10 5:22 PM, "Trevor Daniels" wrote:
>>>
>>>
>>> Neil Puttock wrote Monday, August 09, 2010 9:07 PM
>>>
>>>
On 6 August 2010 20:36, Trevor Daniels
wrote:
> Second, thi
On 16 December 2010 00:05, Carl Sorensen 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
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
Timi
On 10 August 2010 01:08, Carl Sorensen wrote:
> On 8/9/10 5:22 PM, "Trevor Daniels" wrote:
>>
>>
>> Neil Puttock wrote Monday, August 09, 2010 9:07 PM
>>
>>
>>> On 6 August 2010 20:36, Trevor Daniels
>>> wrote:
>>>
Second, this only seems to work in the Score context.
I don't know if t
On 8/9/10 5:22 PM, "Trevor Daniels" wrote:
>
>
> Neil Puttock wrote Monday, August 09, 2010 9:07 PM
>
>
>> On 6 August 2010 20:36, Trevor Daniels
>> 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'
Neil Puttock wrote Monday, August 09, 2010 9:07 PM
On 6 August 2010 20:36, Trevor Daniels
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
On 6 August 2010 20:36, Trevor Daniels 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 intrac
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"
changeBeamin
n
from vacation to check this out.
Trevor
- Original Message - From: "Nick Payne"
To: "Trevor Daniels"
Cc: "lilypond-user"
Sent: Thursday, August 05, 2010 1:03 PM
Subject: Re: Beam settings in 2.13.29
Thanks, that works. I assume the com
urn
from vacation to check this out.
Trevor
- Original Message -
From: "Nick Payne"
To: "Trevor Daniels"
Cc: "lilypond-user"
Sent: Thursday, August 05, 2010 1:03 PM
Subject: Re: Beam settings in 2.13.29
Thanks, that works. I assume the command to reve
((1 . 48) . (6 6 6 6) % beamExceptions
to change the beaming exceptions.
Trevor
- Original Message - From: "Nick Payne"
To: "lilypond-user"
Sent: Thursday, August 05, 2010 1:22 AM
Subject: Beam settings in 2.13.29
In 2/4 time, in earlier versions I used
chang
tions
to change the beaming exceptions.
Trevor
- Original Message -
From: "Nick Payne"
To: "lilypond-user"
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 = \overrideBeamSetting
On Thu, Aug 5, 2010 at 1:30 AM, Nick Payne 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
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 s
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 grou
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 t
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 bec
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
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 indi
> 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
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
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 ru
})
>
> Trevor
>
> - Original Message - From: "Stefan Thomas"
>
> To: "lilypond-user"
> Sent: Monday, January 05, 2009 3:06 PM
> Subject: beam-settings for triplets and sixtuplets
>
>
>> Dear Lilypond-users,
>> in the following
ng '(end 1 12 * *) 2 4 'Staff)
#(revert-auto-beam-setting '(end 1 12 4 4) 3 4 'Staff)
#})
Trevor
- Original Message -
From: "Stefan Thomas"
To: "lilypond-user"
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-set
Carl D. Sorensen wrote Thursday, December 25, 2008 12:21 AM
On 12/24/08 3:31 PM, "Trevor Daniels" wrote:
Herbert Liechti wrote Tuesday, December 23, 2008 6:40 AM
Neil Puttock schrieb:
2008/12/22 Trevor Daniels :
Reinhold Kainhofer wrote Monday, December 22, 2008 4:22 PM
He sent me the
On 12/24/08 3:31 PM, "Trevor Daniels" wrote:
> Herbert Liechti wrote Tuesday, December 23, 2008 6:40 AM
>
>
>> Neil Puttock schrieb:
>>> 2008/12/22 Trevor Daniels :
>>>
Reinhold Kainhofer wrote Monday, December 22, 2008 4:22 PM
>>>
> He sent me the whole file and the culprit is a
Herbert Liechti wrote Tuesday, December 23, 2008 6:40 AM
Neil Puttock schrieb:
2008/12/22 Trevor Daniels :
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, o
Neil Puttock schrieb:
> 2008/12/22 Trevor Daniels :
>
>> 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.be
2008/12/22 Trevor Daniels :
>
> 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 ha
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
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 PianoSt
-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
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 no
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
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
> be
-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
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
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
-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
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.beat
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)
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
[EMAIL PROTECTED] writes:
> 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:
>
> ---
> 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'
> }
> }
> -
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'
}
}
---
48 matches
Mail list logo
