Re: ChangeStaff was: OverrideBeamSettings

2011-01-16 Thread Helge Kruse
Am 16.01.2011 10:35, schrieb Helge Kruse: Am 16.01.2011 10:27, schrieb Helge Kruse: Am 15.01.2011 18:06, schrieb David Kastrup: David Kastrup writes: [...] ud=#(define-music-function (parser location low high) (ly:music? ly:music?) #{ \change Staff = "down" $low \change Staff = "up" $high #})

Re: overrideBeamSettings

2011-01-16 Thread Helge Kruse
Am 16.01.2011 11:25, schrieb Xavier Scheuer: It does not change the output for a Stem #'length = #11 but you'll see the difference if Stem #'length = #18 for instance. With \override Stem #'cross-staff = ##t the vertical spacing between staves is not modified whereas it is if ##f . Ah, I

Re: overrideBeamSettings

2011-01-16 Thread Xavier Scheuer
On 16 January 2011 10:52, Helge Kruse wrote: > > Thanks for the example with the octavated C notes. Your link show a similar > example. Well, I played a bit with the overrides and could see how some of > them work. For this > \override Stem #'cross-staff = ##t > I could not see any difference if

Re: overrideBeamSettings

2011-01-16 Thread Helge Kruse
Am 16.01.2011 10:16, schrieb Xavier Scheuer: On 16 January 2011 09:52, Helge Kruse wrote: Thanks a lot, Xavier. I agree staff changes are annoying, but this should help the harp player to choose the right hand for the notes and so it is sensible. Since I have a lot of these stuff, Is there a w

Re: ChangeStaff was: OverrideBeamSettings

2011-01-16 Thread Helge Kruse
Am 16.01.2011 10:27, schrieb Helge Kruse: Am 15.01.2011 18:06, schrieb David Kastrup: David Kastrup writes: [...] ud=#(define-music-function (parser location low high) (ly:music? ly:music?) #{ \change Staff = "down" $low \change Staff = "up" $high #}) Oops, I forget one important thing. The

Re: ChangeStaff was: OverrideBeamSettings

2011-01-16 Thread Helge Kruse
Am 15.01.2011 18:06, schrieb David Kastrup: David Kastrup writes: [...] ud=#(define-music-function (parser location low high) (ly:music? ly:music?) #{ \change Staff = "down" $low \change Staff = "up" $high #}) global={ \key es\major \time 2/4 } \new StaffGroup << \set StaffGroup.

Re: overrideBeamSettings

2011-01-16 Thread Xavier Scheuer
On 16 January 2011 09:52, Helge Kruse wrote: > > Thanks a lot, Xavier. I agree staff changes are annoying, but this should > help the harp player to choose the right hand for the notes and so it is > sensible. Since I have a lot of these stuff, Is there a way for a scheme > function like this: > >

Re: overrideBeamSettings

2011-01-16 Thread Helge Kruse
Am 15.01.2011 11:31, schrieb Xavier Scheuer: On 15 January 2011 07:03, Helge Kruse wrote: I have tried to set this excerpt from a score but failed with some problems: 1) As you can see there is a staff change again and again. It's annoying to switch as shown below. Can this be done better?

Re: OverrideBeamSettings

2011-01-15 Thread David Kastrup
David Kastrup writes: [...] > global={ \key es\major >\time 2/4 \override Beam #'auto-knee-gap = #4 } Oops. When one uses the original pitches instead of using the wrong octave, you don't need to fiddle with auto-knee-gap to get your result. ud=#(define-music-function (parser location lo

Re: OverrideBeamSettings

2011-01-15 Thread David Kastrup
f change does not work in the first measure (when you > remove the "s2"). > > 3) I tried a lot with the beaming. But I never managed to get a common > beam for all four chords. I read NR 1.2.3 but did not catch what the > arguments to overrideBeamSettings do. It would be nic

Re: overrideBeamSettings

2011-01-15 Thread Xavier Scheuer
mon-notation-for-keyboards.html#changing-staff-manually NR 5.1.3 Keeping contexts alive http://lilypond.org/doc/v2.13/Documentation/notation/keeping-contexts-alive > 3) I tried a lot with the beaming. But I never managed to get a common beam > for > all four chords. I read NR 1.2.3 but did

overrideBeamSettings

2011-01-14 Thread Helge Kruse
2"). 3) I tried a lot with the beaming. But I never managed to get a common beam for all four chords. I read NR 1.2.3 but did not catch what the arguments to overrideBeamSettings do. It would be nice if you can give me a working example. But I am much more interested to_understand_ this th

Re: overrideBeamSettings not working in 2.13.30

2010-08-19 Thread Hans Aberg
On 19 Aug 2010, at 16:25, Carl Sorensen wrote: ... this does not work: music = \new Staff << { \time 9/16 \set beatStructure = #'(4 3 2) \repeat unfold 9 {a'16} } { \time 9/16 \set beatStructure = #'(4 2 3) \repeat unfold 9 {c''16} } Though this does: music = \new Staff << \new Voice

Re: overrideBeamSettings not working in 2.13.30

2010-08-19 Thread Carl Sorensen
On 8/19/10 8:17 AM, "Hans Aberg" wrote: > On 19 Aug 2010, at 15:38, Carl Sorensen wrote: > >> beatStructure is set *per voice*, and since you have parallel music >> in the >> staff, you are creating 3 different voices in the staff, one of >> which has >> #'(4 2 3) beaming but no notes. By us

Re: overrideBeamSettings not working in 2.13.30

2010-08-19 Thread Hans Aberg
On 19 Aug 2010, at 15:38, Carl Sorensen wrote: beatStructure is set *per voice*, and since you have parallel music in the staff, you are creating 3 different voices in the staff, one of which has #'(4 2 3) beaming but no notes. By using braces to combine things sequentially instead of in pa

Re: overrideBeamSettings not working in 2.13.30

2010-08-19 Thread Carl Sorensen
On 8/19/10 3:12 AM, "Hans Aberg" wrote: > > It appears when I do this (MIDI part not necessary - just shows > motivation for code setup): > > \version "2.13.30" > > music = \new Staff << > \time 9/16 > \set beatStructure = #'(4 2 3) > % \set beatStructure = #'(4 3 2) > \repeat unfold 9 {

Re: overrideBeamSettings not working in 2.13.30

2010-08-19 Thread Hans Aberg
On 19 Aug 2010, at 05:24, Carl Sorensen wrote: If you don't want to do \overrideTimeSignatureSettings, it would be sufficient to do \time 9/16 \set beatStructure = #'(4 2 3) because the \time call resets beatStructure. That does not work: I get 3+3+3 on that one, too. So perhaps there is a b

Re: overrideBeamSettings not working in 2.13.30

2010-08-18 Thread Carl Sorensen
On 8/18/10 10:45 AM, "Hans Aberg" wrote: > On 18 Aug 2010, at 17:50, Carl Sorensen wrote: > >> >> If you don't want to do \overrideTimeSignatureSettings, it would be >> sufficient to do >> >> \time 9/16 >> \set beatStructure = #'(4 2 3) >> >> because the \time call resets beatStructure. >

Re: overrideBeamSettings not working in 2.13.30

2010-08-18 Thread Hans Aberg
On 18 Aug 2010, at 17:50, Carl Sorensen wrote: It was not so difficult, it seems (I'll have to check it more). For the 9/16 meter, because there is already a beat structure defined for it (3+3+3), I had to write \overrideTimeSignatureSettings #'Score #'(9 . 16) % time signature fraction #'

Re: overrideBeamSettings not working in 2.13.30

2010-08-18 Thread Carl Sorensen
On 8/18/10 6:20 AM, "Trevor Daniels" wrote: > > > Hans Aberg wrote Wednesday, August 18, 2010 12:17 PM > > >> On 18 Aug 2010, at 11:45, Trevor Daniels wrote: >> >>>> I just switched from LilyPond 2.13.30 (from 2.13.27), and then: >>&g

Re: overrideBeamSettings not working in 2.13.30

2010-08-18 Thread Hans Aberg
On 18 Aug 2010, at 14:20, Trevor Daniels wrote: It was not so difficult, it seems (I'll have to check it more). For the 9/16 meter, because there is already a beat structure defined for it (3+3+3), I had to write \overrideTimeSignatureSettings #'Score #'(9 . 16) % time signature fractio

Re: overrideBeamSettings not working in 2.13.30

2010-08-18 Thread Trevor Daniels
Hans Aberg wrote Wednesday, August 18, 2010 12:17 PM On 18 Aug 2010, at 11:45, Trevor Daniels wrote: I just switched from LilyPond 2.13.30 (from 2.13.27), and then: error: unknown escaped string: `\overrideBeamSettings' The changes are quite extensive. Best to read the Not

Re: overrideBeamSettings not working in 2.13.30

2010-08-18 Thread Hans Aberg
On 18 Aug 2010, at 11:45, Trevor Daniels wrote: I just switched from LilyPond 2.13.30 (from 2.13.27), and then: error: unknown escaped string: `\overrideBeamSettings' So what's the replacement? I used measures like: \overrideBeamSettings #'Score #'(9 . 16) #'en

Re: overrideBeamSettings not working in 2.13.30

2010-08-18 Thread Trevor Daniels
Hans Aberg wrote Wednesday, August 18, 2010 10:08 AM I just switched from LilyPond 2.13.30 (from 2.13.27), and then: error: unknown escaped string: `\overrideBeamSettings' So what's the replacement? I used measures like: \overrideBeamSettings #'Score #'(9 . 16)

overrideBeamSettings not working in 2.13.30

2010-08-18 Thread Hans Aberg
I just switched from LilyPond 2.13.30 (from 2.13.27), and then: error: unknown escaped string: `\overrideBeamSettings' So what's the replacement? I used measures like: \overrideBeamSettings #'Score #'(9 . 16) #'end #'((* . (4 2 3))) __