Re: Overriding Y-extent of Clef doesn't work with v2.17.10
Thomas Morley thomasmorley65 at googlemail.com writes:
in some situations I used to override the Y-extent of the Clef.
With 2.17.10 it doesn't work any more.
I noticed this, too, and found the change that caused it.
https://lists.gnu.org/archive/html/lilypond-user/2013-01/msg00559.html
Now that I think more about it, I see a reasonable way to make it work again:
verticalSpace = {
\override Staff.Clef #'minimum-Y-extent = #'(-20 . 20)
\override Staff.Clef #'vertical-skylines = #'() }
This is good, because it minimum-X-extent is very useful for getting extra
space just where you need it.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
score in a music function?
Dear community,
is it possible to have the score command in a music function?
I need it for a piece with different movements.
I've tried it with the following code which doesn't work:
\version 2.16.2
TheScore = #(define-music-function (parser location x y) (ly:music?
ly:music?)
#{
\score {
\new StaffGroup
\new Staff \with { instrumentName = first } $x
\new Staff \with { instrumentName = second } $y
}
#})
first = \relative c' { c4 d e f g1 }
second = \relative c'' { g4 f e d c1 }
\TheScore \first \second
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: score in a music function?
Stefan Thomas kontrapunktste...@gmail.com writes:
Dear community,
is it possible to have the score command in a music function?
A music function returns music. Use a scheme function to return
arbitrary Scheme.
I need it for a piece with different movements.
I've tried it with the following code which doesn't work:
\version 2.16.2
TheScore = #(define-music-function (parser location x y) (ly:music?
ly:music?)
#{
\score {
\new StaffGroup
\new Staff \with { instrumentName = first } $x
\new Staff \with { instrumentName = second } $y
}
#})
Why don't you just return the StaffGroup here? That's music.
I don't have 2.16 installed, but with current versions
\version 2.16.2
TheScore = #(define-scheme-function (parser location x y) (ly:music?
ly:music?)
#{
\score {
\new StaffGroup
\new Staff \with { instrumentName = first } $x
\new Staff \with { instrumentName = second } $y
}
#})
first = \relative c' { c4 d e f g1 }
second = \relative c'' { g4 f e d c1 }
\score { \TheScore \first \second }
appears to work. Of course, if you are going to have to write
\score { ... } anyway, the incentive for not just using a music function
is not all that high.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bassoon fingering charts O_o
On Feb 6, 2013 4:46 PM, Wim van Dommelen m...@wimvd.nl wrote: Hi James, Note that the Lilypond diagrams are different, not such squarisch, see the notation reference manual for details. The notation reference is the first place I went. Those details were helpful to get me started, but didn't answer my questions. From the list for all bassoon keys, I just produced a diagram usiong the Lilypond diagram showing each and every of the keys, see PDF attached. Thanks -- this saved me hours. I grasped the syntax from the NR, but was confused about where the names appear in the diagram. Big help! Thanks -- hjh ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
hidden notes causing semiquaver stems to lengthen
Dear LilyPond users,
I frequently have to layer many horizontal brackets over a small number of
notes (motivic analysis), and to do this I use extra voices with hidden
notes. Mostly this works fine, but sometimes the hidden notes cause some
odd behaviour with stem lengths in the main part. I've pasted a tinyish
example at the end of this message which should reproduce it.
In the past I've used a variety of workarounds, such as choosing hidden
notes that are far away from the main ones (in the example below, if you
raise the hidden notes by two octaves the problem disappears, but extra
space is added above the staff), or sometimes by removing the stem stencil
of the hidden notes, but these solutions don't always work, so I'd like to
understand what's going on a bit more. If anyone can shed some light it
would solve many problems for me.
Regards,
Kevin Barry
\version 2.16.1
melody = \relative c'' {
d16\startGroup e c\stopGroup d b
}
bracketsa = \relative c'' {
\override NoteColumn #'ignore-collision = ##t
\hideNotes
s8 c16\startGroup d b\stopGroup
}
\score {
\new Staff
\new Voice { \melody }
\new Voice { \bracketsa }
}
\layout {
\context {
\Voice
\consists Horizontal_bracket_engraver
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Overriding Y-extent of Clef doesn't work with v2.17.10
On 6 févr. 2013, at 09:31, Keith OHara k-ohara5...@oco.net wrote:
Thomas Morley thomasmorley65 at googlemail.com writes:
in some situations I used to override the Y-extent of the Clef.
With 2.17.10 it doesn't work any more.
I noticed this, too, and found the change that caused it.
https://lists.gnu.org/archive/html/lilypond-user/2013-01/msg00559.html
Now that I think more about it, I see a reasonable way to make it work again:
verticalSpace = {
\override Staff.Clef #'minimum-Y-extent = #'(-20 . 20)
\override Staff.Clef #'vertical-skylines = #'() }
This is good, because it minimum-X-extent is very useful for getting extra
space just where you need it.
There is also:
\override Staff.Clef #'vertical-skylines =
#ly:grob::simple-vertical-skylines-from-extents
which uses the extent of the clef instead of the shape to calculate vertical
skylines.
Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
add9 chords
Hi all, I've searching for a way to add 'add9' chords to my own version of predefined fretboards, but whatever I do, it does not accept it and doesn't render it. I think the system doesn't allow 'add9' as chordname, because when I change it to '9', like 'c:9' it does render. How can I solve this? I'm using both 9 and add9 chords for my guitarbook, and do need both, so using c:9 to describe c:add9 is quite confusing. I know I can modify chordnames, and in the chordnames I can get c:add9, but not in the fretboards. I do need the fretboards for these chords, it is a teaching book and I don't want to break the consistency. Grtz, Bart http://www.bartart3d.be/ On facebook https://www.facebook.com/pages/BartArt3D/169488999795102 On Twitter https://twitter.com/#%21/Bart_Issimo On Identi.ca http://identi.ca/bartart3d On Google+ https://plus.google.com/u/0/b/116379400376517483499/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
Hi Bart, Lily's behaviour is quite correct. c:9 will produce a c major triad plus the ninth, ie c e g d' ... that's an add9 chord. A proper ninth chord is c e g bf d', ie a stack of thirds. Thus, you'll need c:7.9 for a 9 chord. You can check it out if you put your chords in an ordinary Staff to see the notes. Best, Robert On 6 Feb 2013, at 13:40, bart deruyter bart.deruy...@gmail.com wrote: Hi all, I've searching for a way to add 'add9' chords to my own version of predefined fretboards, but whatever I do, it does not accept it and doesn't render it. I think the system doesn't allow 'add9' as chordname, because when I change it to '9', like 'c:9' it does render. How can I solve this? I'm using both 9 and add9 chords for my guitarbook, and do need both, so using c:9 to describe c:add9 is quite confusing. I know I can modify chordnames, and in the chordnames I can get c:add9, but not in the fretboards. I do need the fretboards for these chords, it is a teaching book and I don't want to break the consistency. Grtz, Bart http://www.bartart3d.be/ On facebook On Twitter On Identi.ca On Google+ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
Hi, Am 2013-02-06 13:40, schrieb bart deruyter: I've searching for a way to add 'add9' chords to my own version of predefined fretboards, but whatever I do, it does not accept it and doesn't render it. I think the system doesn't allow 'add9' as chordname, because when I change it to '9', like 'c:9' it does render. Use c:9^7 Regards Jan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
Did you try c:5.9? On Wed, Feb 6, 2013 at 1:40 PM, bart deruyter bart.deruy...@gmail.comwrote: Hi all, I've searching for a way to add 'add9' chords to my own version of predefined fretboards, but whatever I do, it does not accept it and doesn't render it. I think the system doesn't allow 'add9' as chordname, because when I change it to '9', like 'c:9' it does render. How can I solve this? I'm using both 9 and add9 chords for my guitarbook, and do need both, so using c:9 to describe c:add9 is quite confusing. I know I can modify chordnames, and in the chordnames I can get c:add9, but not in the fretboards. I do need the fretboards for these chords, it is a teaching book and I don't want to break the consistency. Grtz, Bart http://www.bartart3d.be/ On facebook https://www.facebook.com/pages/BartArt3D/169488999795102 On Twitter https://twitter.com/#%21/Bart_Issimo On Identi.ca http://identi.ca/bartart3d On Google+ https://plus.google.com/u/0/b/116379400376517483499/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- *Nesmotren govori kao da mačem probada, a jezik je mudrih iscjeljenje. Izreke 12:18* ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
\set additionalPitchPrefix = #add
within \chordmode renders the chord name with add9 instead of 9 only.
Example:
\version 2.16.0
cd = \chordmode {
\set additionalPitchPrefix = #add
c1:9 c:9^7 c:5.9
}
\new ChordNames \cd
\new FretBoards \cd
\new Staff \cd
Am 06.02.2013 13:40, schrieb bart deruyter:
Hi all,
I've searching for a way to add 'add9' chords to my own version of
predefined fretboards, but whatever I do, it does not accept it and
doesn't render it. I think the system doesn't allow 'add9' as chordname,
because when I change it to '9', like 'c:9' it does render.
How can I solve this? I'm using both 9 and add9 chords for my
guitarbook, and do need both, so using c:9 to describe c:add9 is quite
confusing.
I know I can modify chordnames, and in the chordnames I can get c:add9,
but not in the fretboards. I do need the fretboards for these chords, it
is a teaching book and I don't want to break the consistency.
Grtz,
Bart
http://www.bartart3d.be/
On facebook https://www.facebook.com/pages/BartArt3D/169488999795102
On Twitter https://twitter.com/#%21/Bart_Issimo
On Identi.ca http://identi.ca/bartart3d
On Google+ https://plus.google.com/u/0/b/116379400376517483499/
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: score in a music function?
Dear David,
I also use version 2.16.2
But Your example doesn't work for me.
I get the error message
partiturtest.ly:17:34: Fehler: syntax error, unexpected '} \score {
\TheScore \first \second}
I don't have 2.16 installed, but with current versions
\version 2.16.2
TheScore = #(define-scheme-function (parser location x y) (ly:music?
ly:music?)
#{
\score {
\new StaffGroup
\new Staff \with { instrumentName = first } $x
\new Staff \with { instrumentName = second } $y
}
#})
first = \relative c' { c4 d e f g1 }
second = \relative c'' { g4 f e d c1 }
\score { \TheScore \first \second }
appears to work. Of course, if you are going to have to write
\score { ... } anyway, the incentive for not just using a music function
is not all that high.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: score in a music function?
Stefan Thomas kontrapunktste...@gmail.com writes:
Dear David,
I also use version 2.16.2
But Your example doesn't work for me.
I get the error message
partiturtest.ly:17:34: Fehler: syntax error, unexpected '} \score {
\TheScore \first \second}
Looks more like a copypaste error than anything else. Non-breaking
spaces or something?
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Repeat signs / bar lines in markup
Hi List, is there some way to put bar lines, or more specifically repeat signs, inside a text markup? Other than recreating them with the help of \draw-line and \draw-circle? -- Peter Crighton | Musician Music Engraver based in Mainz, Germany http://www.petercrighton.de ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: score in a music function?
2013/2/6 Stefan Thomas kontrapunktste...@gmail.com:
Sorry, I can't find the mistake!
Here's my code:
\version 2.16.2
TheScore = #(define-scheme-function (parser location x y) (ly:music?
ly:music?)
#{
\score {
\new StaffGroup
\new Staff \with { instrumentName = first } $x
\new Staff \with { instrumentName = second } $y
}
#})
first = \relative c' { c4 d e f g1 }
second = \relative c'' { g4 f e d c1 }
\score { \TheScore \first \second }
2013/2/6 David Kastrup d...@gnu.org
Stefan Thomas kontrapunktste...@gmail.com writes:
Dear David,
I also use version 2.16.2
But Your example doesn't work for me.
I get the error message
partiturtest.ly:17:34: Fehler: syntax error, unexpected '} \score {
\TheScore \first \second}
Looks more like a copypaste error than anything else. Non-breaking
spaces or something?
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
David's suggestion works fine with 2.17.10
For 2.16.1 changing to _music_-function and deleting the
\score-command from the function seems to work:
\version 2.16.1
TheScore = #(define-music-function (parser location x y) (ly:music? ly:music?)
#{
\new StaffGroup
\new Staff \with { instrumentName = first } $x
\new Staff \with { instrumentName = second } $y
#})
first = \relative c' { c4 d e f g1 }
second = \relative c'' { g4 f e d c1 }
\score { \TheScore \first \second }
Or, if you insist on a _scheme_-function,delete the \score-command
from the function and add
... in the final \score-call.
\version 2.16.1
TheScore = #(define-scheme-function (parser location x y) (ly:music? ly:music?)
#{
\new StaffGroup
\new Staff \with { instrumentName = first } $x
\new Staff \with { instrumentName = second } $y
#})
first = \relative c' { c4 d e f g1 }
second = \relative c'' { g4 f e d c1 }
\score { \TheScore \first \second }
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Point and click in music-function
2013/2/4 David Kastrup d...@gnu.org
I have created
URL:http://code.google.com/p/lilypond/issues/detail?id=3153 which will
let all the music created within #{ ... #} point to \tr. That's pretty
much the best you can hope to do with reasonable effort.
Ah that's great I will try this, when a Lilypond version with this change
is available.
I have tried this with the code in you last mail. But this doesn't change
the behavior. Obviously I don't have sufficient Scheme skills:
tr = #(define-music-function (parser location p1 p2 p3)
(ly:pitch? ly:pitch? ly:pitch?)
music-map
(lambda (m)
(set! (ly:music-property m 'origin) location))
#{ \times 2/3 { $p1 8 [ $p2 $p3 ] } #})
A more precise
solution would only be possible by tacking source information onto
_every_ music function argument and tracing its progress in expressions,
quite more expensive and actually also ill-defined: what is the
point-and-click location for the note generated by $p1 8 ? What is the
location for the beam?
It would be nice to get the exact position of the note in the source. But
when the click gets me to the \tr it would be very helpful. I will await
the version including the change.
Thanks
Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Point and click in music-function
Helge Kruse helge.kr...@gmx.net writes:
2013/2/4 David Kastrup d...@gnu.org
I have created
URL:http://code.google.com/p/lilypond/issues/detail?id=3153
which will
let all the music created within #{ ... #} point to \tr. That's
pretty
much the best you can hope to do with reasonable effort.
Ah that's great I will try this, when a Lilypond version with this
change is available.
I have tried this with the code in you last mail. But this doesn't
change the behavior. Obviously I don't have sufficient Scheme skills:
tr = #(define-music-function (parser location p1 p2 p3)
(ly:pitch? ly:pitch? ly:pitch?)
music-map
(lambda (m)
(set! (ly:music-property m 'origin) location))
#{ \times 2/3 { $p1 8 [ $p2 $p3 ] } #})
That's rather a lack of copypaste skills. You can't add or remove
parentheses in Scheme without changing the meaning.
A more precise
solution would only be possible by tacking source information onto
_every_ music function argument and tracing its progress in
expressions,
quite more expensive and actually also ill-defined: what is the
point-and-click location for the note generated by $p1 8 ? What is
the
location for the beam?
It would be nice to get the exact position of the note in the source.
But there is no such thing as a note in the source. There is just a
_pitch_. The _note_ is only assembled inside of the #{...#}.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
hm, thanks for all the tips, but:
- c:9 produces a C9, including the seventh, (sorry Robert Schmaus, I just
tested it)
- c:7.9 renders a C9, including seventh too
- C:9^7 produces a C7 chord (just tried it Robert Kohnert).
- Using: \set additionalPitchPrefix = #add only changes the chord name,
not the diagram.
using lilypond version 1.17.6
I need the diagram of a Cadd9, not C9.
Adding:
\addChordShape #'c:add9 #guitar-tuning #x;3-3;2-2;o;3-4;o;
\storePredefinedDiagram #default-fret-table \chordmode {c:add9}
#guitar-tuning
#(chord-shape 'c:add guitar-tuning)
to the predefined chordlist does not work, since c:add9 is not accepted by
lilypond as a chord name, when I change the name to c:9 it does render this
diagram, but it also shows the chord name as C9, while it is a Cadd9.
Really no solution for a Cadd9? I guess this must be a bug then...
http://www.bartart3d.be/
On facebook https://www.facebook.com/pages/BartArt3D/169488999795102
On Twitter https://twitter.com/#%21/Bart_Issimo
On Identi.ca http://identi.ca/bartart3d
On Google+ https://plus.google.com/u/0/b/116379400376517483499/
2013/2/6 Noeck noeck.marb...@gmx.de
\set additionalPitchPrefix = #add
within \chordmode renders the chord name with add9 instead of 9 only.
Example:
\version 2.16.0
cd = \chordmode {
\set additionalPitchPrefix = #add
c1:9 c:9^7 c:5.9
}
\new ChordNames \cd
\new FretBoards \cd
\new Staff \cd
Am 06.02.2013 13:40, schrieb bart deruyter:
Hi all,
I've searching for a way to add 'add9' chords to my own version of
predefined fretboards, but whatever I do, it does not accept it and
doesn't render it. I think the system doesn't allow 'add9' as chordname,
because when I change it to '9', like 'c:9' it does render.
How can I solve this? I'm using both 9 and add9 chords for my
guitarbook, and do need both, so using c:9 to describe c:add9 is quite
confusing.
I know I can modify chordnames, and in the chordnames I can get c:add9,
but not in the fretboards. I do need the fretboards for these chords, it
is a teaching book and I don't want to break the consistency.
Grtz,
Bart
http://www.bartart3d.be/
On facebook https://www.facebook.com/pages/BartArt3D/169488999795102
On Twitter https://twitter.com/#%21/Bart_Issimo
On Identi.ca http://identi.ca/bartart3d
On Google+ https://plus.google.com/u/0/b/116379400376517483499/
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
force flat beam in piano staff that uses \autochange
Dear All, I have a piano staff that is using \autochange. The notes are just running 16ths throughout. In a beamed group, sometimes the notes are all in the upper staff, sometimes they are all in the lower staff, and sometimes they are in both. What I really want to do is force the beam to be flat and centered between the two staves. Is this possible? Many thanks in advance, Mike ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
allowing any horizontal collision in proportional notation
Dear All, It seems that with proportional notation even strict spanning does not allow collisions of notehead and accidentals. Is it possible to allow any collision such that the resolution and accuracy are exact no matter what? Or maybe I am missing something Many thanks in advance, Mike ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
Hi there, Am Mittwoch, 6. Februar 2013, 21:54:57 schrieb bart deruyter: - c:9 produces a C9, including the seventh, (sorry Robert Schmaus, I just tested it) yes, thats perfectly correct, since 9 means 7th and 9th. :) - c:7.9 renders a C9, including seventh too this is the same command as above… - C:9^7 produces a C7 chord (just tried it Robert Kohnert). This is working here using Lily 2.14.2, but I've set \semiGermanChords in the chord section, maybe that changes the behaviour. If the above command produces a 7th instead of an add9 (the '^' removes the following note, not the previous one), this was either changed in some development version (maybe some developer can help about that) or I consider it to be a bug. using lilypond version 1.17.6 You mean 2.17.6, don't you? 1.X cannot even be decribed by the term ancient (though I started with some 1.X version…). :) -- MfG Jan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
lol, indeed, 2.17.6... so the search continues... I was hoping to get it by trying out c:2 for diagram, and splitting chordnames and and chord diagrams, and using \set additionalPitchPrefix = #add, but c:2 renders a Csus2 diagram.. bummer getting quite completely stuck here... http://www.bartart3d.be/ On facebook https://www.facebook.com/pages/BartArt3D/169488999795102 On Twitter https://twitter.com/#%21/Bart_Issimo On Identi.ca http://identi.ca/bartart3d On Google+ https://plus.google.com/u/0/b/116379400376517483499/ 2013/2/6 Jan Kohnert nospam001-li...@jankoh.dyndns.org Hi there, Am Mittwoch, 6. Februar 2013, 21:54:57 schrieb bart deruyter: - c:9 produces a C9, including the seventh, (sorry Robert Schmaus, I just tested it) yes, thats perfectly correct, since 9 means 7th and 9th. :) - c:7.9 renders a C9, including seventh too this is the same command as above… - C:9^7 produces a C7 chord (just tried it Robert Kohnert). This is working here using Lily 2.14.2, but I've set \semiGermanChords in the chord section, maybe that changes the behaviour. If the above command produces a 7th instead of an add9 (the '^' removes the following note, not the previous one), this was either changed in some development version (maybe some developer can help about that) or I consider it to be a bug. using lilypond version 1.17.6 You mean 2.17.6, don't you? 1.X cannot even be decribed by the term ancient (though I started with some 1.X version…). :) -- MfG Jan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: force flat beam in piano staff that uses \autochange
On 07/02/13 07:57, Michael Winter wrote:
Dear All,
I have a piano staff that is using \autochange. The notes are just running
16ths throughout. In a beamed group, sometimes the notes are all in the upper
staff, sometimes they are all in the lower staff, and sometimes they are in
both. What I really want to do is force the beam to be flat and centered
between the two staves. Is this possible?
This will force all beams to be between
\version 2.16.2
\new PianoStaff {
\autochange {
\relative c'' {
\override Beam #'positions = #'(4.5 . 4.5)
b16 b b,, b
}
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
Am 06.02.2013 22:24, schrieb bart deruyter:
lol, indeed, 2.17.6... so the search continues...
I was hoping to get it by trying out c:2 for diagram, and splitting
chordnames and and chord diagrams, and using \set
additionalPitchPrefix = #add,
but c:2 renders a Csus2 diagram.. bummer getting quite completely
stuck here...
If I understand you right, the code below should be a solution.
The valid chord in chordmode is either c:5.9 or c:9^7 and you can't
change that. But you can change how it is printed as chord name and you
can define your fret diagram. Both is shown below.
Btw, my last mail already showed that a Cadd9 (c5.9) has a different
fret diagram than a C9 (c:9) chord.
HTH,
Joram
\version 2.16.0
\addChordShape #'c:5.9 #guitar-tuning #x;3-3;2-2;o;3-4;o;
\storePredefinedDiagram #default-fret-table \chordmode {c:5.9}
#guitar-tuning
#(chord-shape 'c:5.9 guitar-tuning)
cd = \chordmode {
\set additionalPitchPrefix = #add
c1:9 c:9^7 c:5.9
}
\new ChordNames \cd
\new FretBoards \cd
\new Staff \cd
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
Hi,
Am Mittwoch, 6. Februar 2013, 22:24:32 schrieb bart deruyter:
lol, indeed, 2.17.6... so the search continues...
OK, might be a change in the development version…
I was hoping to get it by trying out c:2 for diagram, and splitting
chordnames and and chord diagrams, and using \set additionalPitchPrefix
= #add,
but c:2 renders a Csus2 diagram.. bummer getting quite completely stuck
here...
I created a minimal example, which works fine here using 2.14, you can test it
and post the results (you probably need to convert-ly it first…)
Maybe we can get a clue then…
(Just tested: removing inclusion of deutsch.ly and \semiGermanChord does not
change the correctness here…)
--
MfG Jan\version 2.14.0
\include deutsch.ly
\include predefined-guitar-fretboards.ly
gtrharmony = \chordmode {
\semiGermanChords
g1 c:9^7
}
melody = \relative c'' {
\key g \major
g1 c
}
\score {
\new FretBoards \gtrharmony
\context ChordNames = chords \gtrharmony
\context Staff = voice
\new Voice { \voiceFour \melody }
}
attachment: list.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
@Noeck: thanks for the help, was just working on that solution. Indeed,
that seems to be the way to go.
It's sad thought that 'add' is not accepted by \storepredifineddiagram in a
chord name.
It would have made things quite a bit easier for a chord that is, in my
opinion, used quite often.
I'll put this on the 'wishlist' for lilypond :-).
Grtz,
Bart
http://www.bartart3d.be/
On facebook https://www.facebook.com/pages/BartArt3D/169488999795102
On Twitter https://twitter.com/#%21/Bart_Issimo
On Identi.ca http://identi.ca/bartart3d
On Google+ https://plus.google.com/u/0/b/116379400376517483499/
2013/2/6 Noeck noeck.marb...@gmx.de
Am 06.02.2013 22:24, schrieb bart deruyter:
lol, indeed, 2.17.6... so the search continues...
I was hoping to get it by trying out c:2 for diagram, and splitting
chordnames and and chord diagrams, and using \set
additionalPitchPrefix = #add,
but c:2 renders a Csus2 diagram.. bummer getting quite completely
stuck here...
If I understand you right, the code below should be a solution.
The valid chord in chordmode is either c:5.9 or c:9^7 and you can't
change that. But you can change how it is printed as chord name and you
can define your fret diagram. Both is shown below.
Btw, my last mail already showed that a Cadd9 (c5.9) has a different
fret diagram than a C9 (c:9) chord.
HTH,
Joram
\version 2.16.0
\addChordShape #'c:5.9 #guitar-tuning #x;3-3;2-2;o;3-4;o;
\storePredefinedDiagram #default-fret-table \chordmode {c:5.9}
#guitar-tuning
#(chord-shape 'c:5.9 guitar-tuning)
cd = \chordmode {
\set additionalPitchPrefix = #add
c1:9 c:9^7 c:5.9
}
\new ChordNames \cd
\new FretBoards \cd
\new Staff \cd
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: force flat beam in piano staff that uses \autochange
On 07/02/13 07:57, Michael Winter wrote:
Dear All,
I have a piano staff that is using \autochange. The notes are just running
16ths throughout. In a beamed group, sometimes the notes are all in the upper
staff, sometimes they are all in the lower staff, and sometimes they are in
both. What I really want to do is force the beam to be flat and centered
between the two staves. Is this possible?
Sorry. Accidentally pressed send too soon on previous msg. Override the
beam damping.
\version 2.16.2
\new PianoStaff {
\autochange {
\relative c'' {
\override Beam #'damping = #+inf.0
b16 b b,, b
b b b'' b
}
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: force flat beam in piano staff that uses \autochange
Am 06.02.2013 22:47, schrieb Nick Payne:
\new PianoStaff {
\autochange {
\relative c'' {
\override Beam #'positions = #'(4.5 . 4.5)
b16 b b,, b
}
}
}
Do you mean, #'(-4.5 . -4.5) ?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
2013/2/6 bart deruyter bart.deruy...@gmail.com:
It's sad thought that 'add' is not accepted by \storepredifineddiagram in a
chord name.
How about:
\version 2.16.1
% \version 2.17.10
chExceptionMusic = {
c e g d'1-\markup { \super add9 }
}
chExceptions = #(append
(sequential-music-to-chord-exceptions chExceptionMusic #t)
ignatzekExceptions)
\include predefined-guitar-fretboards.ly
\storePredefinedDiagram #default-fret-table
\chordmode { c:1.3.5.9 }
#guitar-tuning
#x;3-3;2-2;o;3-4;o;
chrds =
\chordmode {
\set chordNameExceptions = #chExceptions
c:1.3.5.9
c:9
c:7
c
}
\new ChordNames \chrds
\new FretBoards \chrds
\new Staff \chrds
HTH,
Harm
attachment: atest-22.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Percussion Snippet
Hallo,
is there a standard solution to improve the following snippet from
the docs?
% cut pasted from LilyPond — Notation Reference for version 2.14.2
#(define mydrums '((hiwoodblock default #t 3)
(lowoodblock default #t -2)))
woodstaff = {
% This defines a staff with only two lines.
% It also defines the positions of the two lines.
\override Staff.StaffSymbol #'line-positions = #'(-2 3)
% This is necessary; if not entered, the barline would be too short!
\override Staff.BarLine #'bar-extent = #'(-1.5 . 1.5)
}
\new DrumStaff {
\set DrumStaff.drumStyleTable = #(alist-hash-table mydrums)
% with this you load your new drum style table
\woodstaff
\drummode {
\time 2/4
wbl8 wbl16 wbl wbh8- wbl |
wbl8 wbl16 wbh- ~ wbh wbl16 r8 |
}
}
(http://lilypond.org/doc/v2.14/Documentation/13/lily-66415f8b.ly)
Martin
attachment: lily-ce79488a.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: force flat beam in piano staff that uses \autochange
This does not work when there are groups of notes beamed together that are
either all in the upper staff or in the lower staff. I assume it would only
work if you could guarantee that all notes grouped under a beam have notes in
both the upper and lower staves.
thanks,
Mike
On Feb 6, 2013, at 4:10 PM, lilypond-user-requ...@gnu.org wrote:
Message: 2
Date: Thu, 07 Feb 2013 08:58:22 +1100
From: Nick Payne nick.pa...@internode.on.net
To: lilypond-user@gnu.org
Subject: Re: force flat beam in piano staff that uses \autochange
Message-ID: 5112d1fe.4090...@internode.on.net
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 07/02/13 07:57, Michael Winter wrote:
Dear All,
I have a piano staff that is using \autochange. The notes are just running
16ths throughout. In a beamed group, sometimes the notes are all in the
upper staff, sometimes they are all in the lower staff, and sometimes they
are in both. What I really want to do is force the beam to be flat and
centered between the two staves. Is this possible?
Sorry. Accidentally pressed send too soon on previous msg. Override the
beam damping.
\version 2.16.2
\new PianoStaff {
\autochange {
\relative c'' {
\override Beam #'damping = #+inf.0
b16 b b,, b
b b b'' b
}
}
}
--
Message: 3
Date: Wed, 06 Feb 2013 22:58:28 +0100
From: Noeck noeck.marb...@gmx.de
To: lilypond-user@gnu.org
Subject: Re: force flat beam in piano staff that uses \autochange
Message-ID: 5112d204.3080...@gmx.de
Content-Type: text/plain; charset=UTF-8
Am 06.02.2013 22:47, schrieb Nick Payne:
\new PianoStaff {
\autochange {
\relative c'' {
\override Beam #'positions = #'(4.5 . 4.5)
b16 b b,, b
}
}
}
Do you mean, #'(-4.5 . -4.5) ?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Percussion Snippet
2013/2/7 Martin Bergande m.berga...@gmx.net: is there a standard solution to improve the following snippet from the docs? Please try to be a little more specific! What isn't sufficient? What should be improved? -Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: disabling point-and-click for displayed chords?
On Sat, Jan 26, 2013 at 10:04 PM, Adam Spiers
lilypond-u...@adamspiers.org wrote:
On Tue, Jan 15, 2013 at 3:05 PM, Adam Spiers
lilypond-u...@adamspiers.org wrote:
On Tue, Jan 15, 2013 at 9:41 AM, David Kastrup d...@gnu.org wrote:
You could use an engraver in ChordNames for wiping out the (event) cause
of the last involved grob. Then the point-and-click location would no
longer be available...
That makes sense. Do you mean an existing engraver though, or a new
one? The only existing one which looks promising is
Output_property_engraver (which I had never heard of before). Does
that mean I do this via \applyOutput?
I got this to work for a single note via:
#(define (delete-grob-cause grob origctx curctx)
(let* ((cause (ly:grob-property grob 'cause))
(music-origin (if (ly:stream-event? cause)
(ly:event-property cause 'origin
(ly:debug removing grob origin '~a' music-origin)))
(ly:grob-set-property! grob 'cause #f))
and then:
\applyOutput #'ChordNames #delete-grob-cause
However, this only worked for the single note following the command.
I searched hard for a way to apply it to all notes, but this was the
best advice I could find:
http://thread.gmane.org/gmane.comp.gnu.lilypond.general/18699/focus=18700
and both options presented were behind my expertise.
I eventually found a solution to this:
(music-map
(lambda (x)
(let ((type (ly:music-property x 'name)))
(if (eq? type 'NoteEvent)
#{ \applyOutput #'Score #delete-grob-cause $x #}
#{ $x #}))
) music))
This is possibly worth an LSR entry, although in the end, Jan helped
me come up with a fundamentally superior approach to the whole
problem, documented here:
https://github.com/aspiers/ly2video/issues/16
I think it would be worth either extending \pointAndClickTypes to
support filtering by context, or adding a new command such as
\pointAndClickContexts. If there is agreement with this idea I am
happy to submit an issue and drum up a patch, but I'd appreciate
guidance on the best interface syntax. For instance, I'm not sure
whether it's better to treat the argument as a list of contexts to
include:
\pointAndClickExcludedContexts #'(Voice DrumVoice)
or contexts to exclude:
\pointAndClickContexts #'(ChordNames)
or should both inclusion and exclusion be supported, either via
separate commands or a single command, e.g.
\pointAndClickContexts #'(Voice DrumVoice -ChordNames)
And how would any of these commands interact with the existing
\pointAndClickTypes command? Presumably they'd have to be treated as
an additional level of filtering.
I still think this line of development is still worthwhile, but I'm
unlikely to have time to drive it.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: force flat beam in piano staff that uses \autochange
On 07/02/13 12:39, Michael Winter wrote:
This does not work when there are groups of notes beamed together that
are either all in the upper staff or in the lower staff. I assume it
would only work if you could guarantee that all notes grouped under a
beam have notes in both the upper and lower staves.
Works here. The beams are flat regardless of which stave(s) the notes
occupy. If you mean that you only want the beams forced flat where the
notes occupy both staves, then decide which is more frequent (notes
grouped on one stave or both), and use \once\override for the others.
e.g. if kneed beams are more frequent:
\version 2.16.2
nf = \once\override Beam #'damping = #1 % back to default
\new PianoStaff {
\autochange {
\relative c'' {
\override Beam #'damping = #+inf.0
b16 b b,, b
b b b'' b
\nf b cis d e
b b b,, b
}
}
}
p.s. I tried using \once\revert Beam #'damping: no error was indicated
but the \once is ignored...
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: add9 chords
Hi Bart, - c:9 produces a C9, including the seventh, (sorry Robert Schmaus, I just tested it) Oh ... I think there have been some changes from the previous stable version (2.14) then. I had the problem that I could *not* produce 11 or 9 chords - I always got the add9 or add11 version, until somebody informed me that I need to specify the full chord, including the 7. Now (in version 2.16 and 2.17), we have * c : 9 produces c e g bf d' and the chord name is C9 * c : 7.9 produces the same * c : 9^7 produces c e g d' (but the chord name still is C9 - you can check this on http://lilybin.com/jtiz8e/1 ) I liked the old way better. Sure, it's cumbersome to write c : 7.9.11.13 for a 13 chord, but at least there was full control over the chord. At the very least, c : 9^7 should not be called C9. And, again, it used to be that way in previous versions. Best, Robert ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
