Re: Flat flags
2013/10/2 Gilberto Agostinho gilbertohasn...@googlemail.com: Hi Harm, Thank you so much for this code. I realize now that it was not your flat-flag code that wasn't matching the old and modern-straight-flags, but actually it was the notes using \set stemLeftBeamCount x[] that were not matching them! Now I see that by using \set stemLeftBeamCount, the flags behave just like beams that were cut in half, and the position of beams are slightly differently than the normal flags. Thus I do not think it is necessary to play around with the stem length values. So thank you once again for all your help. Best regards, Gilberto Hi Gilberto, I made a patch about it. Should be in next devel-release. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Piano music switching staves
@Ben I was trying to make the example as simple as possible so I omitted all that stuff but I can put it back in when I get home. I tried using the example in the documentation but it just added another staff -- View this message in context: http://lilypond.1069038.n5.nabble.com/Piano-music-switching-staves-tp152147p152153.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ugly bar line when changing line-count
Gilberto Agostinho wrote And still one more little problem concerning changes in line-count: if the line-count is changed in the middle of a bar, they tend to be modified only after an accidental! Have a look on the following code: On the top staff, everything is fine between accidental and staff lines. But on the bottom staff, the lines extend more than they should, leaving the accidentals with the old number of lines and the notes with the new number of lines. for me this behavior seems as expected and you can easily tweak the cases where you'd like it differently - look at the attached code to see how to: http://lilypond.1069038.n5.nabble.com/file/n152154/test4.png test4.ly http://lilypond.1069038.n5.nabble.com/file/n152154/test4.ly Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/ugly-bar-line-when-changing-line-count-tp152072p152154.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Lyric-Staff-spacing fails with smaller lyrics
Hello list,
I want to place lyrics above and below a certain staff which works
perfectly as long as I do not change the size of staff and lyrics,
see the attached file and its resulting pdf.
Interestingly, it seems that tin example 2, the upper lyrics are
farther away in the first line, whereas the lower lyrics are farther
away in the second line.
How can I achieve the narrower lyrics from example 1 with the smaller
lyrics and staves of example 2?
TIA,
Marc
\version 2.17.29
\pointAndClickOff
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set Staff.fontSize = #new-size
\override Staff.StaffSymbol #'staff-space = #(magstep new-size)
\override Staff.StaffSymbol #'thickness = #(magstep new-size)
#})
lyricSize = #(define-music-function (parser location new-size) (number?)
#{
\override Score.LyricText.font-size = #new-size
#})
LyrUp = \lyricmode {
\repeat unfold 8 { lyr -- ics on top }
}
LyrDown = \lyricmode {
\repeat unfold 8 { bot -- tom lyr -- ics }
}
MelUp = {
\repeat unfold 8 { d''8 b' b' b' r2 }
}
MelDown = {
\repeat unfold 8 { r2 g'8 b' b' b' }
}
\score {
\new Staff = test
\with { instrumentName = TestStaff }
\new Voice = up { \voiceOne \MelUp }
\new Voice = down { \voiceTwo \MelDown }
\new Lyrics
\with { alignAboveContext = #test }
\lyricsto up \LyrUp
\new Lyrics \lyricsto down \LyrDown
}
\score {
\new Staff = test
\with { \staffSize #-4 instrumentName = TestStaff }
\new Voice = up { \voiceOne \MelUp }
\new Voice = down { \voiceTwo \MelDown }
\new Lyrics
\with { \lyricSize #-4 alignAboveContext = #test }
\lyricsto up \LyrUp
\new Lyrics
\with { \lyricSize #-4 }
\lyricsto down \LyrDown
}
lyric-problem.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cresc. whitespace padding
Thomas Morley-2 wrote
Also possible:
\version 2.16.2
moreVerticalDynamicTextSpannerWhiteoutII =
#(define-music-function (parser location adds)(pair?)
(define (flexible-stencil-whiteout add stencil)
(let*
((x-ext (ly:stencil-extent stencil X))
(y-ext (ly:stencil-extent stencil Y)))
(ly:stencil-add
(stencil-with-color
(ly:round-filled-box
(interval-widen x-ext (car add))
(interval-widen y-ext (cdr add))
0.0)
white)
stencil)))
(define more-stencil-whiteout
(lambda (grob)
(let* ((stil (ly:line-spanner::print grob))
(x-ext (ly:stencil-extent stil X))
(y-ext (ly:stencil-extent stil Y))
(whiteout-stil (flexible-stencil-whiteout adds stil)))
(ly:make-stencil
(ly:stencil-expr whiteout-stil)
x-ext
y-ext
#{
%% Needed for 2.17.x:
\override DynamicTextSpanner #'vertical-skylines = #'()
\once \override DynamicTextSpanner #'stencil =
#more-stencil-whiteout
#})
\score {
\new GrandStaff
\new Staff
\relative c' {
c d e
\moreVerticalDynamicTextSpannerWhiteoutII #'(0 . 1.5)
f \cresc c d e f \!
}
\new Staff
\relative c' {
c d e f \cresc c d e f \!
}
}
'moreVerticalDynamicTextSpannerWhiteoutII' doesn't affect the vertical
spacing of other grobs.
To see the the difference, try higher values for y in
\moreVerticalDynamicTextSpannerWhiteoutII #'(x . y)
Cheers,
Harm
Wow this is a fantastically useful function! Thank you for that, it's
definitely helped with my understanding of how scheme works, too.
Anyone else agree that this would be a very good addition to the snippet
repository?
Damnit David, I'm a musician not a programmer! In all seriousness though I
always do my best to figure out the answer myself via the documentation. I
know I've asked a far few questions over the past week but believe me there
are a lot that I've not posted because I've spent hours reading through the
manual and snippets. I'm very conscious about only using the mailing list as
a last resort instead of a short-cut to problems I could solve myself, and
I'm sorry if I've not given that impression!
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/cresc-whitespace-padding-tp152120p152156.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyric-Staff-spacing fails with smaller lyrics
Marc Hohl wrote
Hello list,
I want to place lyrics above and below a certain staff which works
perfectly as long as I do not change the size of staff and lyrics,
see the attached file and its resulting pdf.
Interestingly, it seems that tin example 2, the upper lyrics are
farther away in the first line, whereas the lower lyrics are farther
away in the second line.
How can I achieve the narrower lyrics from example 1 with the smaller
lyrics and staves of example 2?
I don't think LP fails, it's just that the vertical spacing isn't corrected
with the \staffSize macro (which btw can be simplified to
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol #'staff-space = #(magstep new-size)
\override StaffSymbol #'thickness = #(magstep new-size)
#})
and then it can be used in any context owning a font size engraver)
to control the vertical spacing just specify
\new Lyrics \with {
\staffSize #-4 alignAboveContext = #test
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing = #'(
(basic-distance . 2)
(padding . 1)
)
}
or similar
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Lyric-Staff-spacing-fails-with-smaller-lyrics-tp152155p152157.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cresc. whitespace padding
EdBeesley edplaysdr...@gmail.com writes: Damnit David, I'm a musician not a programmer! In all seriousness though I always do my best to figure out the answer myself via the documentation. Good. Then you can tell us where the documentation falls short. To be exact, I reacted to your statement: Now when you say this could be easily turned into a music-function... could we assume for a second that I'm totally dumb and have no idea how to do this? And my answer to that was: That's where LilyPond's documentation could come in handy... You are in obvious disagreement: I know I've asked a far few questions over the past week but believe me there are a lot that I've not posted because I've spent hours reading through the manual and snippets. I'm very conscious about only using the mailing list as a last resort instead of a short-cut to problems I could solve myself, and I'm sorry if I've not given that impression! So let's see where 5 minutes (we are not talking hours here) with the manual will take us. I first look up music function in the Notation Reference's index and find URL:http://lilypond.org/doc/v2.16/Documentation/notation/using-music-functions#index-Music-functions Going straight to the second section substitution function examples (assuming that I am dumb and the first section Substitution function syntax scares me) from there, the very first example illustrates how to wrap a code passage taking numerical values as arguments into a music function. So obviously you got stuck elsewhere in your attempt to solve that problem yourself in the hour between the time the non-parametric solution was posted and you asked for getting a solution using a function. Where? How can we improve the documentation so that anybody faced with the same task, namely wrapping some code with parameters into a music function, is not still floored after having been given the right keywords? Could we assume for a second that I'm totally clueless and have no idea how to do this? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Piano/Xylophone key diagrams
At college, one of my ensembles is a mixed-music group performing modern music. I normally get away with singing or playing a triangle and bits of other untuned percussion. Imagine my surprised when I was given a xylophone piece to play. Fortunately, it's only one note at a time, and most of them are the same note, repeated for four bars, so I generally have the time to work out where the next key is when I'm playing the current one. However, I thought it might be interesting and vaguely useful to have some piano key diagrams which show which key is to be played, rather like the fingering diagrams. The attached image illustrates the kind of thing: playing D#. I know I could use box, rounded-box or filled-box, or moveto/lineto commands to draw the boxes, so I clearly could create the diagrams individually for each note. However, I thought it would be better to create a function to do this. I'd presume the location of each box would be in some sort of array/list, and that the function would use the 'pitch of the note to determine which to fill. However, I've read our documentation on scheme and am stuck on how to start, either creating the array/list and iterating over it to draw boxes, or grabbing the pitch value of a note. Could anyone start me off on this and help when I get stuck again? TIA. -- Phil Holmes attachment: Keys.png___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Aligning output question
One of the last hurdles I have to figure out to start producing course
notes is to Left/Right jusify staff output, if it is possible. I've done
some document scanning and not found my solution. Would anyone be able
to point me in the right direction or check my input code to see if it
even has the right structure. Here it is...
\version 2.16.2
% BasicNoteTabTemplate.ly
\language english
\header {
%title = First String Practice
%composer = Composer
%subtitle = English with Guitar
}
song = {
e1 f g e f g e f g f e \bar |.
}
\new Staff \relative c'' {
\numericTimeSignature \time 4/4
\song
}
\new TabStaff \relative c' {
%\override Stem #'transparent = ##t
%\override Beam #'transparent = ##t
\song
}
\new Staff \relative c'' {
\numericTimeSignature \time 4/4
e2 e f f g g e e f f g g e e f f g g f f e e \bar |.
}
\new TabStaff \relative c' {
%\override Stem #'transparent = ##t
%\override Beam #'transparent = ##t
e2 e f f g g e e f f g g e e f f g g f f e e \bar |.
}
Another guestion is about variable usage. Can variables be changed or
are they equivalent to constants?
Namaste,
Kevin Tough
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Piano/Xylophone key diagrams
Phil Holmes em...@philholmes.net writes: At college, one of my ensembles is a mixed-music group performing modern music. I normally get away with singing or playing a triangle and bits of other untuned percussion. Imagine my surprised when I was given a xylophone piece to play. Fortunately, it's only one note at a time, and most of them are the same note, repeated for four bars, so I generally have the time to work out where the next key is when I'm playing the current one. However, I thought it might be interesting and vaguely useful to have some piano key diagrams which show which key is to be played, rather like the fingering diagrams. The attached image illustrates the kind of thing: playing D#. I know I could use box, rounded-box or filled-box, or moveto/lineto commands to draw the boxes, so I clearly could create the diagrams individually for each note. However, I thought it would be better to create a function to do this. I'd presume the location of each box would be in some sort of array/list, and that the function would use the 'pitch of the note to determine which to fill. However, I've read our documentation on scheme and am stuck on how to start, either creating the array/list and iterating over it to draw boxes, or grabbing the pitch value of a note. Could anyone start me off on this and help when I get stuck again? Starting off would be on URL:http://code.google.com/p/lilypond/issues/detail?id=3563#c4. Check its output. This is basically what you need, except that you need to replace the C-Griff function which uses filled and non-filled circles in a three-row arrangement with a more tedious rectangular arrangement. The c-griff function here only does the formatting and would need to be completely replaced. In contrast, the stuff in define-scheme-function could be kept unchanged. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyric-Staff-spacing fails with smaller lyrics
Am 12.10.2013 13:42, schrieb Eluze:
Marc Hohl wrote
Hello list,
I want to place lyrics above and below a certain staff which works
perfectly as long as I do not change the size of staff and lyrics,
see the attached file and its resulting pdf.
Interestingly, it seems that tin example 2, the upper lyrics are
farther away in the first line, whereas the lower lyrics are farther
away in the second line.
How can I achieve the narrower lyrics from example 1 with the smaller
lyrics and staves of example 2?
I don't think LP fails, it's just that the vertical spacing isn't corrected
with the \staffSize macro (which btw can be simplified to
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol #'staff-space = #(magstep new-size)
\override StaffSymbol #'thickness = #(magstep new-size)
#})
and then it can be used in any context owning a font size engraver)
to control the vertical spacing just specify
\new Lyrics \with {
\staffSize #-4 alignAboveContext = #test
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing = #'(
(basic-distance . 2)
(padding . 1)
)
}
or similar
Thanks! I'll give it a try as soon as possible.
The idea with fontSize looks neat, thank you for
pointing this out!
Still I don't quite understand why the distances seem to change
between the first and the second line of the second example.
Marc
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aligning output question
Am 12.10.2013 15:09, schrieb Kevin Tough:
One of the last hurdles I have to figure out to start producing course
notes is to Left/Right jusify staff output, if it is possible. I've done
some document scanning and not found my solution. Would anyone be able
to point me in the right direction or check my input code to see if it
even has the right structure. Here it is...
\version 2.16.2
% BasicNoteTabTemplate.ly
\language english
\header {
%title = First String Practice
%composer = Composer
%subtitle = English with Guitar
}
song = {
e1 f g e f g e f g f e \bar |.
}
\new Staff \relative c'' {
\numericTimeSignature \time 4/4
\song
}
Though it is some sort of nitpicking, I'd use
song = \relative c' { ... }
here, and include it by
\new Staff {
\clef treble_8
\song
}
\new TabStaff {
\song
}
The octavated treble clef is recommended for guitar music while
the little '8' is more often than not omitted.
Marc
[...]
Another guestion is about variable usage. Can variables be changed or
are they equivalent to constants?
Something like
song = \relative c'' { c1 d e f }
\score {
\new Staff { \song }
}
song = \relative c'' { g1 a b c }
\score {
\new Staff { \song }
}
?
Just give it a try ;-)
Marc
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aligning output question
Kevin Tough ke...@toughlife.org writes: One of the last hurdles I have to figure out to start producing course notes is to Left/Right jusify staff output, if it is possible. I can't figure out what you want. Another guestion is about variable usage. Can variables be changed or are they equivalent to constants? Again, that question makes it very hard to figure out what you want. A variable of course can be changed. That's the whole point of it being a variable. You are probably talking about changing music expressions. Music expressions can be changed (and many music functions liberally do so with its arguments), but if you write \song you get a _copy_ of the music expression in \song already, so any changes done on an argument provided with \song does not affect the original value in the variable song. You can revert to Scheme to do modify the expression in song in-place, but that's bad style. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Piano/Xylophone key diagrams
2013/10/12 David Kastrup d...@gnu.org: Phil Holmes em...@philholmes.net writes: At college, one of my ensembles is a mixed-music group performing modern music. I normally get away with singing or playing a triangle and bits of other untuned percussion. Imagine my surprised when I was given a xylophone piece to play. Fortunately, it's only one note at a time, and most of them are the same note, repeated for four bars, so I generally have the time to work out where the next key is when I'm playing the current one. However, I thought it might be interesting and vaguely useful to have some piano key diagrams which show which key is to be played, rather like the fingering diagrams. The attached image illustrates the kind of thing: playing D#. I know I could use box, rounded-box or filled-box, or moveto/lineto commands to draw the boxes, so I clearly could create the diagrams individually for each note. However, I thought it would be better to create a function to do this. I'd presume the location of each box would be in some sort of array/list, and that the function would use the 'pitch of the note to determine which to fill. However, I've read our documentation on scheme and am stuck on how to start, either creating the array/list and iterating over it to draw boxes, or grabbing the pitch value of a note. Could anyone start me off on this and help when I get stuck again? Starting off would be on URL:http://code.google.com/p/lilypond/issues/detail?id=3563#c4. Check its output. This is basically what you need, except that you need to replace the C-Griff function which uses filled and non-filled circles in a three-row arrangement with a more tedious rectangular arrangement. The c-griff function here only does the formatting and would need to be completely replaced. In contrast, the stuff in define-scheme-function could be kept unchanged. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user Or maybe http://lsr.dsi.unimi.it/LSR/Item?id=791 might give some inspiration. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Piano/Xylophone key diagrams
Thomas Morley thomasmorle...@gmail.com writes: 2013/10/12 David Kastrup d...@gnu.org: Phil Holmes em...@philholmes.net writes: Could anyone start me off on this and help when I get stuck again? Starting off would be on URL:http://code.google.com/p/lilypond/issues/detail?id=3563#c4. Check its output. This is basically what you need, except that you need to replace the C-Griff function which uses filled and non-filled circles in a three-row arrangement with a more tedious rectangular arrangement. The c-griff function here only does the formatting and would need to be completely replaced. In contrast, the stuff in define-scheme-function could be kept unchanged. Or maybe http://lsr.dsi.unimi.it/LSR/Item?id=791 might give some inspiration. Or you can plug one into the other. Basically you are only one (map (lambda (x) (list-ref '(c cis d dis e f fis g gis a bes b c' cis' ...) x)) pressed) away from mapping the pressed input into what that snippet wants as input. The output, though, is a lot more piano-specific than what Phil proposed as diagram. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LibreOffice, Latex Docs ?? Documenting Lilypond's *.pdf output
Kevin Tough kevin at toughlife.org writes: As a Lilypond newbie in what direction should I be looking to be able to create documentation including Lilypond's pdf output. Inserting the *.pdfs into Libre Office in Fedora seems to be a dead end, at least directly. Create encapsulated postscript images with the eps backend and insert the eps-files as images into your LibreOffice document. lilypond --ps -d backend=eps On Linux and Mac, inserting eps images is no problem at all; I believe that on Windows, LibreOffice will recognize and use ghostscript if you have installed it. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cresc. whitespace padding
David Kastrup wrote EdBeesley lt; edplaysdrums@ gt; writes: Damnit David, I'm a musician not a programmer! In all seriousness though I always do my best to figure out the answer myself via the documentation. Good. Then you can tell us where the documentation falls short. To be exact, I reacted to your statement: Now when you say this could be easily turned into a music-function... could we assume for a second that I'm totally dumb and have no idea how to do this? And my answer to that was: That's where LilyPond's documentation could come in handy... You are in obvious disagreement: I know I've asked a far few questions over the past week but believe me there are a lot that I've not posted because I've spent hours reading through the manual and snippets. I'm very conscious about only using the mailing list as a last resort instead of a short-cut to problems I could solve myself, and I'm sorry if I've not given that impression! So let's see where 5 minutes (we are not talking hours here) with the manual will take us. I first look up music function in the Notation Reference's index and find lt;URL:http://lilypond.org/doc/v2.16/Documentation/notation/using-music-functions#index-Music-functionsgt; Going straight to the second section substitution function examples (assuming that I am dumb and the first section Substitution function syntax scares me) from there, the very first example illustrates how to wrap a code passage taking numerical values as arguments into a music function. So obviously you got stuck elsewhere in your attempt to solve that problem yourself in the hour between the time the non-parametric solution was posted and you asked for getting a solution using a function. Where? How can we improve the documentation so that anybody faced with the same task, namely wrapping some code with parameters into a music function, is not still floored after having been given the right keywords? Could we assume for a second that I'm totally clueless and have no idea how to do this? -- David Kastrup I'm sensing a certain level of hostility here which I don't think is completely deserved I'm assuming from your experience and knowledge that you are a programmer first and foremost? So for example if you saw the first solution and then consulted the suggested entries in the manual you'd immediately spot the connections and be able to figure out how to create your own function. Whereas I saw the entry in the manual and just thought 'where the hell do I go from here'. I'm sure part of that was tiredness, as this was after 9 hours of typesetting, but were it not for the example kindly provided by Thomas I imagine I'd still be no wiser today. How to solve this? Ideally make it so I don't have to delve into complex code to do things like this. But then that depends on what the target market of Lilypond is... If it's for professional typesetters (e.g. people who use winScore) then absolutely they should be expected to have intimate knowledge of the inner workings of Lilypond to enable them work out how to do all the complex and crazy things they no doubt have to do on a daily basis. But if you're after your average Sibelius/Finale user who just wants nicer looking music than those 2 programs can offer but doesn't want to have to spend hours and hours (and it /has/ taken me hours and hours to get even a basic understanding of how Lilypond works, and I don't regard my level of stupidity as particularly above average) on figuring out how to do things that aren't documented directly yet, (e.g. this whitespace thing I originally posted about) then I think necessitating this level of knowledge will switch a lot of people off. Speaking personally if it wasn't for the fantastic level of support I've received from all the generous people on this mailing list then I simply wouldn't have bothered with Lilypond in the first place, as I don't have the time to spend working stuff out that someone else can answer in 10 seconds. I know the point of the manual/tutorials is to enable me to work things out easily, but, as I mentioned earlier, sometimes you look at things and without a programmer's mindset it just looks insurmountable. Has anyone ever broached the topic of a subscription help-line forum or something like that? If there was a way I could pay a subscription fee and then get suggested snippets like the above without having to spend time trying to work it out first I would sign up immediately. This way I wouldn't have to feel guilty about asking a question and people with superior knowledge would get more than just a thank you for their time... -- View this message in context: http://lilypond.1069038.n5.nabble.com/cresc-whitespace-padding-tp152120p152167.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org
Re: Aligning output question
Hi Marc,
I just cleaned up my code as you suggested, thanks.
My input file puts out 2 pairs of staffs. One with whole notes and one
with half notes. Is it possible to vertically align both the start and
end length of the two pairs? This is just a piece of a larger file with
5 pairs of staffs. They all have different lengths and it just does not
look very professional.
As a newbie to Lilypond I just take the output and use GIMP to convert
it into an image format that Libre Office supports. I hope not to have
to create separate output for each staff pair (notes + tab) to achieve
the formatting I'd like.
Namaste,
Kevin
On Sat, 2013-10-12 at 15:20 +0200, Marc Hohl wrote:
Am 12.10.2013 15:09, schrieb Kevin Tough:
One of the last hurdles I have to figure out to start producing course
notes is to Left/Right jusify staff output, if it is possible. I've done
some document scanning and not found my solution. Would anyone be able
to point me in the right direction or check my input code to see if it
even has the right structure. Here it is...
\version 2.16.2
% BasicNoteTabTemplate.ly
\language english
\header {
%title = First String Practice
%composer = Composer
%subtitle = English with Guitar
}
song = {
e1 f g e f g e f g f e \bar |.
}
\new Staff \relative c'' {
\numericTimeSignature \time 4/4
\song
}
Though it is some sort of nitpicking, I'd use
song = \relative c' { ... }
here, and include it by
\new Staff {
\clef treble_8
\song
}
\new TabStaff {
\song
}
The octavated treble clef is recommended for guitar music while
the little '8' is more often than not omitted.
Marc
[...]
Another guestion is about variable usage. Can variables be changed or
are they equivalent to constants?
Something like
song = \relative c'' { c1 d e f }
\score {
\new Staff { \song }
}
song = \relative c'' { g1 a b c }
\score {
\new Staff { \song }
}
?
Just give it a try ;-)
Marc
___
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: cresc. whitespace padding
- Original Message - From: EdBeesley edplaysdr...@gmail.com To: lilypond-user@gnu.org Sent: Saturday, October 12, 2013 2:45 PM Subject: Re: cresc. whitespace padding David Kastrup wrote EdBeesley lt; edplaysdrums@ gt; writes: Damnit David, I'm a musician not a programmer! In all seriousness though I always do my best to figure out the answer myself via the documentation. Good. Then you can tell us where the documentation falls short. To be exact, I reacted to your statement: Now when you say this could be easily turned into a music-function... could we assume for a second that I'm totally dumb and have no idea how to do this? And my answer to that was: That's where LilyPond's documentation could come in handy... You are in obvious disagreement: I know I've asked a far few questions over the past week but believe me there are a lot that I've not posted because I've spent hours reading through the manual and snippets. I'm very conscious about only using the mailing list as a last resort instead of a short-cut to problems I could solve myself, and I'm sorry if I've not given that impression! So let's see where 5 minutes (we are not talking hours here) with the manual will take us. I first look up music function in the Notation Reference's index and find lt;URL:http://lilypond.org/doc/v2.16/Documentation/notation/using-music-functions#index-Music-functionsgt; Going straight to the second section substitution function examples (assuming that I am dumb and the first section Substitution function syntax scares me) from there, the very first example illustrates how to wrap a code passage taking numerical values as arguments into a music function. So obviously you got stuck elsewhere in your attempt to solve that problem yourself in the hour between the time the non-parametric solution was posted and you asked for getting a solution using a function. Where? How can we improve the documentation so that anybody faced with the same task, namely wrapping some code with parameters into a music function, is not still floored after having been given the right keywords? Could we assume for a second that I'm totally clueless and have no idea how to do this? -- David Kastrup I'm sensing a certain level of hostility here which I don't think is completely deserved I don't think it was intended. The problem is that the documentation for Lilypond is generally excellent and occasionally useless. Regular contributors get a little tired of users who can't be bothered to read the bits that are excellent, and instead ask here (often repeatedly asking questions that are trivially solved with a quick R of TFM). David was at pains to request suggestions on how to improve an aspect of the documentation that you have found useless for your purposes. Has anyone ever broached the topic of a subscription help-line forum or something like that? If there was a way I could pay a subscription fee and then get suggested snippets like the above without having to spend time trying to work it out first I would sign up immediately. This way I wouldn't have to feel guilty about asking a question and people with superior knowledge would get more than just a thank you for their time... http://lilypond.org/sponsoring.html -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cresc. whitespace padding
EdBeesley edplaysdr...@gmail.com writes:
[...]
I'm sensing a certain level of hostility here which I don't think is
completely deserved I'm assuming from your experience and knowledge
that you are a programmer first and foremost?
You mean, as opposed to a human being?
So for example if you saw the first solution
No. I just picked the keywords that Thomas Morley provided and looked
in the index of the manual for them. Without even bothering to look at
the first solution.
and then consulted the suggested entries in the manual you'd
immediately spot the connections and be able to figure out how to
create your own function.
The manual gives the example:
URL:http://lilypond.org/doc/v2.16/Documentation/notation/substitution-function-examples
padText =
#(define-music-function
(parser location padding)
(number?)
#{
\once \override TextScript #'padding = #padding
#})
\relative c''' {
c4^piu mosso b a b
\padText #1.8
c4^piu mosso d e f
\padText #2.6
c4^piu mosso fis a g
}
Which could be considered suffering from a bit of overuse of padding
both as symbol and as argument, if we are assuming no previous clue
about what this may be about. It probably would have helped if the
non-function version of the code was written out before that.
Whereas I saw the entry in the manual and just thought 'where the hell
do I go from here'.
It helps if you _mention_ what manual entry you did not get along with
and why if you want to avoid the impression that you did not actually
look.
How to solve this? Ideally make it so I don't have to delve into
complex code to do things like this. But then that depends on what the
target market of Lilypond is... If it's for professional typesetters
(e.g. people who use winScore) then absolutely they should be expected
to have intimate knowledge of the inner workings of Lilypond to enable
them work out how to do all the complex and crazy things they no doubt
have to do on a daily basis.
You _totally_ evade the question about how the manual entry (or its
navigation) could have been improved to actually make you not require
additional help. Instead you insist that programmers or whoever else
should feel responsible for manually solving your problems.
But if you're after your average Sibelius/Finale user who just wants
nicer looking music than those 2 programs can offer but doesn't want
to have to spend hours and hours (and it /has/ taken me hours and
hours to get even a basic understanding of how Lilypond works, and I
don't regard my level of stupidity as particularly above average) on
figuring out how to do things that aren't documented directly yet,
(e.g. this whitespace thing I originally posted about) then I think
necessitating this level of knowledge will switch a lot of people off.
So how about pointing out _particular_ problems? A rant is very nice
and all, but it does not help us improve our documentation.
Speaking personally if it wasn't for the fantastic level of support
I've received from all the generous people on this mailing list then I
simply wouldn't have bothered with Lilypond in the first place, as I
don't have the time to spend working stuff out that someone else can
answer in 10 seconds.
Didn't playing an instrument require you to work stuff out that someone
else could play just right away? And do you really think that Thomas
Morley invested a mere 10 seconds for each of his very elaborate answers
to you?
I know the point of the manual/tutorials is to enable me to work
things out easily, but, as I mentioned earlier, sometimes you look at
things and without a programmer's mindset it just looks
insurmountable.
So can you point out _what_ exactly looked insurmountable without a
programmer's mindset? And how it could have been made surmountable?
Has anyone ever broached the topic of a subscription help-line forum
or something like that? If there was a way I could pay a subscription
fee and then get suggested snippets like the above without having to
spend time trying to work it out first I would sign up
immediately.
Suggested snippets are both in LilyPond's online manual under
URL:http://www.lilypond.org/doc/v2.16/Documentation/snippets/ as well
as on URL:http://lsr.dsi.unimi.it/.
This way I wouldn't have to feel guilty about asking a question and
people with superior knowledge would get more than just a thank you
for their time...
You'll find that things are even more counterintuitive in that regard
than LilyPond's documentation. At the current point of time, Thomas
Morley is likely the single most helpful help-line person around. Now
you would imagine that this would most likely lead to people paying him
small amounts of money as appreciation.
The reality is rather that he as well as others pay me, probably one of
the less helpful people around here, regularly not so small amounts of
money so that I keep improving LilyPond including its manual.
Because when more people
Re: Lyric-Staff-spacing fails with smaller lyrics
Marc Hohl wrote Still I don't quite understand why the distances seem to change between the first and the second line of the second example. could this be determined by one of the …-…-spacing's!? - Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Lyric-Staff-spacing-fails-with-smaller-lyrics-tp152155p152171.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aligning output question
- Original Message -
From: Kevin Tough ke...@toughlife.org
To: LilypondMailingListGenUser lilypond-user@gnu.org
Sent: Saturday, October 12, 2013 2:09 PM
Subject: Aligning output question
One of the last hurdles I have to figure out to start producing course
notes is to Left/Right jusify staff output, if it is possible.
\paper {
ragged-right = ##f
}
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aligning output question
2013/10/12 Phil Holmes m...@philholmes.net:
- Original Message - From: Kevin Tough ke...@toughlife.org
To: LilypondMailingListGenUser lilypond-user@gnu.org
Sent: Saturday, October 12, 2013 2:09 PM
Subject: Aligning output question
One of the last hurdles I have to figure out to start producing course
notes is to Left/Right jusify staff output, if it is possible.
\paper {
ragged-right = ##f
}
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Perhaps combined with
\paper {
linewidth = what-ever-you-need
}
and/or other settings for paper
http://lilypond.org/doc/v2.17/Documentation/notation-big-page#page-layout
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aligning output question
Thomas Morley thomasmorle...@gmail.com writes:
2013/10/12 Phil Holmes m...@philholmes.net:
- Original Message - From: Kevin Tough ke...@toughlife.org
To: LilypondMailingListGenUser lilypond-user@gnu.org
Sent: Saturday, October 12, 2013 2:09 PM
Subject: Aligning output question
One of the last hurdles I have to figure out to start producing course
notes is to Left/Right jusify staff output, if it is possible.
\paper {
ragged-right = ##f
}
Perhaps combined with
\paper {
linewidth = what-ever-you-need
}
and/or other settings for paper
http://lilypond.org/doc/v2.17/Documentation/notation-big-page#page-layout
In this case, it seems like the main purpose is to to arrange one-line
mini-scores together with text. That sounds more like
\markup { \fill-line { Here is markup
\score { ... \layout { } } } }
so basically using \score inside of \markup, and have \markup describe
the actual material supposed to fill the line including the score
fragment.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cresc. whitespace padding
Hi Ed, 2013/10/12 EdBeesley edplaysdr...@gmail.com: David Kastrup wrote EdBeesley lt; edplaysdrums@ gt; writes: Damnit David, I'm a musician not a programmer! That's true for me, too! :) In all seriousness though I always do my best to figure out the answer myself via the documentation. Good. Then you can tell us where the documentation falls short. To be exact, I reacted to your statement: Now when you say this could be easily turned into a music-function... could we assume for a second that I'm totally dumb and have no idea how to do this? And my answer to that was: That's where LilyPond's documentation could come in handy... You are in obvious disagreement: I know I've asked a far few questions over the past week but believe me there are a lot that I've not posted because I've spent hours reading through the manual and snippets. I'm very conscious about only using the mailing list as a last resort instead of a short-cut to problems I could solve myself, and I'm sorry if I've not given that impression! So let's see where 5 minutes (we are not talking hours here) with the manual will take us. I first look up music function in the Notation Reference's index and find lt;URL:http://lilypond.org/doc/v2.16/Documentation/notation/using-music-functions#index-Music-functionsgt; Going straight to the second section substitution function examples (assuming that I am dumb and the first section Substitution function syntax scares me) from there, the very first example illustrates how to wrap a code passage taking numerical values as arguments into a music function. So obviously you got stuck elsewhere in your attempt to solve that problem yourself in the hour between the time the non-parametric solution was posted and you asked for getting a solution using a function. Where? How can we improve the documentation so that anybody faced with the same task, namely wrapping some code with parameters into a music function, is not still floored after having been given the right keywords? Could we assume for a second that I'm totally clueless and have no idea how to do this? -- David Kastrup I'm sensing a certain level of hostility here which I don't think is completely deserved I'm _sure_ no hostility was intended. If David is abrupt sometimes ... ignore it. And if he (or me or someone else) is in a really bad mood ... ignore it. Read and try to understand what is written, I guarantee you will gain much profit !! Would be nice if you could help us to improve the documentation. So please take David serious (and _not_ offending) and try to reply his question. Please understand that developers and longtime users are very familiar with the docs. Perhaps you can imagine that this might be a _disadvantage_ sometimes. Best, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cresc. whitespace padding
I don't think it was intended. The problem is that the documentation for Lilypond is generally excellent and occasionally useless. Regular contributors get a little tired of users who can't be bothered to read the bits that are excellent, and instead ask here (often repeatedly asking questions that are trivially solved with a quick R of TFM). David was at pains to request suggestions on how to improve an aspect of the documentation that you have found useless for your purposes. I can totally understand that, but believe me I always do my best to read through and try to understand the documentation. I will admit though maybe I didn't try hard enough last night after so much time spent staring at a screen! I'm sensing a certain level of hostility here which I don't think is completely deserved I'm assuming from your experience and knowledge that you are a programmer first and foremost? You mean, as opposed to a human being? Sorry, I put the trailing dots in completely the wrong place. I meant the latter sentence to run into the subsequent one, i.e. you're first and foremost a programmer therefore you spot connections in the manual that non programmers might not. I was not meaning to question your credentials as a human being at any point :) You _totally_ evade the question about how the manual entry (or its navigation) could have been improved to actually make you not require additional help. Instead you insist that programmers or whoever else should feel responsible for manually solving your problems. So how about pointing out _particular_ problems? A rant is very nice and all, but it does not help us improve our documentation. Again, sorry, I went off on a bit of a tangent. Although I think here the internet as a medium for communication is letting us down somewhat; I can assure you I wasn't intending to rant! Trying to answer the question in hindsight is a little tricky, as now I've got the example from Thomas and compared it to the documentation examples (http://lilypond.org/doc/v2.16/Documentation/notation/substitution-function-examples) I almost understand it. I think my main problem last night was that I couldn't figure out how to turn the x-ext and y-ext into variables that could be passed to the function. But looking at it now it almost seems obvious. Perhaps if you could include an example using more complex scheme code like the one Thomas used for this post and show how the fixed values can be replaced by variables that get passed to the function? That would definitely have helped my first reading of it, I think. Speaking personally if it wasn't for the fantastic level of support I've received from all the generous people on this mailing list then I simply wouldn't have bothered with Lilypond in the first place, as I don't have the time to spend working stuff out that someone else can answer in 10 seconds. Didn't playing an instrument require you to work stuff out that someone else could play just right away? If we're using that instrumental simile, then the majority of things a pupil learns he could figure out by himself eventually (a GROSS oversimplification of teaching but let it slide for now!). However, a teacher gives the correct way of doing things first time, and through subsequent practice the pupil then understands the reasons why they are doing things that way, and have saved a lot of time in the process. Also, a teacher gets paid for providing these short cuts (which is what I was proposing). And do you really think that Thomas Morley invested a mere 10 seconds for each of his very elaborate answers to you? I think your literalness and my exaggeration are hindering each other, I was meaning that relatively speaking it took him far far less time to provide the answer than it would have done for me to provide it myself. You'll find that things are even more counterintuitive in that regard than LilyPond's documentation. At the current point of time, Thomas Morley is likely the single most helpful help-line person around. Now you would imagine that this would most likely lead to people paying him small amounts of money as appreciation. I would happily send Thomas some money as thanks for his advice! I would much rather have a structured way of doing this, e.g. I post a topic like this, Thomas says easy, give me 5 bucks I'll tell you how to do it and I send him 5 bucks. I know this is kind of implemented with the bounty system but I get the impression that's for more serious additions to the code. Now you are basically saying that Thomas _wastes_ his money, at least regarding the part where it goes to letting me work on making the manual more human-understandable, because you consider the manual useless: you explicitly state that you will not look anything up that anybody else can solve for you in a reasonably short amount of time, and it's very hard for a manual to compete with _that_. That's a little
Re: cresc. whitespace padding
EdBeesley edplaysdr...@gmail.com writes: I think my main problem last night was that I couldn't figure out how to turn the x-ext and y-ext into variables that could be passed to the function. But looking at it now it almost seems obvious. Perhaps if you could include an example using more complex scheme code like the one Thomas used for this post and show how the fixed values can be replaced by variables that get passed to the function? That would definitely have helped my first reading of it, I think. I don't think replacing a simple example by a more complex one will help, but showing the simple example before turning it into a function might. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Stand alone guitar chord diagrams
First thanks for the help getting started with Lilypond! In my course documentation I will need a flexible means to generate chord diagrams. I would be greatly surprised that Lilypond could be used for this but perhaps someone has experience with this and would make a suggestion as to what I might use. I'm running Linux and would prefer something open source. Namaste, Kevin Tough ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cresc. whitespace padding
David Kastrup wrote EdBeesley lt; edplaysdrums@ gt; writes: I think my main problem last night was that I couldn't figure out how to turn the x-ext and y-ext into variables that could be passed to the function. But looking at it now it almost seems obvious. Perhaps if you could include an example using more complex scheme code like the one Thomas used for this post and show how the fixed values can be replaced by variables that get passed to the function? That would definitely have helped my first reading of it, I think. I don't think replacing a simple example by a more complex one will help, but showing the simple example before turning it into a function might. -- David Kastrup ___ lilypond-user mailing list lilypond-user@ https://lists.gnu.org/mailman/listinfo/lilypond-user Yes, indeed combining/cross linking examples might be very useful. For example you might use Thomas' initial example as an example of modifying a stencil with scheme, and this could be on the page about stencils and the page about scheme code. And there you could link to things you can now do with this new scheme code, e.g. making a function out of it. I definitely wouldn't mind a higher level of hand-holding through some of the more complex parts of the manual. -- View this message in context: http://lilypond.1069038.n5.nabble.com/cresc-whitespace-padding-tp152120p152191.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
no tableofcontents with lilypond-book
Dear community,
I don't get a table of contents with this latex-file, when I compile it
with pdflatex and lilypond-book.
\documentclass[a4paper,10pt]{article}
\usepackage[utf8]{inputenc}
%\newcommand{\betweenLilyPondSystem}[1]{\vspace{36mm}\linebreak} % hier
irgendeinen vernünftig erscheinenden Wert eingeben!!!
\begin{document}
\tableofcontents
\section{c major}
This is the c major scale: \\
\begin[notime]{lilypond}
\relative{c4 d e f g a b c}
\end{lilypond}
\section{g major}
This is the g major scale: \\
\begin[notime]{lilypond}
\relative g'{\key g \major g4 a b c d e fis g}
\end{lilypond}
\end{document}
I compile it with the following bash-script (on Ubuntu):
#!/bin/bash
TEMP_DIR=temp
CURRENT_DIR=$(pwd)
lilypond-book --pdf \
--include=$CURRENT_DIR\
--include=/home/stefan/partituren/lilyponds/vorlagen/\
--output=$TEMP_DIR \
$1.tex \
(cd $TEMP_DIR \
pdflatex $1.tex \
mv $1.pdf ..) \
rm -rf $TEMP_DIR
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: no tableofcontents with lilypond-book
Stefan Thomas kontrapunktste...@gmail.com writes: Dear community, I don't get a table of contents with this latex-file, when I compile it with pdflatex and lilypond-book. (cd $TEMP_DIR \ pdflatex $1.tex \ mv $1.pdf ..) \ rm -rf $TEMP_DIR You won't get a table of contents with _any_ LaTeX file when compiling it only once. Usually it requires two or three passes to get an accurate table of contents, more if you don't have a separate page numbering style for the table of contents (like roman numerals) and the page numbers after the table of contents change depending on its length. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Flat flags
Hi Harm, does the patch fix issue 3096? Karol Dnia 12-10-2013 o godz. 8:26 Thomas Morley napisał(a): 2013/10/2 Gilberto Agostinho gilbertohasn...@googlemail.com: Hi Harm, Thank you so much for this code. I realize now that it was not your flat-flag code that wasn't matching the old and modern-straight-flags, but actually it was the notes using \set stemLeftBeamCount x[] that were not matching them! Now I see that by using \set stemLeftBeamCount, the flags behave just like beams that were cut in half, and the position of beams are slightly differently than the normal flags. Thus I do not think it is necessary to play around with the stem length values. So thank you once again for all your help. Best regards, Gilberto Hi Gilberto, I made a patch about it. Should be in next devel-release. Cheers, Harm ___ 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: laying out plainsong chant
Hi Gabe,
please always reply to the list, because others might also be interested
and in this case I can't help much.
Here is a parametrized version of \longbar which puts it on the line
number pos. However with odd numbers, ledger lines are drawn for the
rest and it looks different. I don't know how to handle this.
The optimal function could be used in this way:
a\longbar instead of \longbar -2
But I don't know how to do that.
Cheers,
Joram
\version 2.17.26
longbar = #(define-music-function (parser location pos) (number?)
#{
\override Rest #'font-size = #4
\override Rest #'staff-position = #pos
r2*1/4
\once \override Rest #'extra-offset = #'(-1.3 . 0)
r2*1/4
\revert Rest #'font-size
\revert Rest #'staff-position
#})
%usage (example)
{
\cadenzaOn
r4 \longbar -2 \longbar 2 \longbar 1 r4
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Flat flags
2013/10/12 Karol Majewski karo...@wp.pl: Hi Harm, does the patch fix issue 3096? Karol No. Though, I've an idea how to tackle 3096. I'll try tomorrow, currently I'm too tired. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: laying out plainsong chant
Hi Ben, Thanks, that helps. When I use the underscore, lilypond is placing the first tick (under the b-flat) lower down than the others; do you know why this is? I would like them to all be parallel. source: https://gist.github.com/gmoothart/6954226 output: https://dl.dropboxusercontent.com/u/84432/chant.pdf TIA, Gabe On Thu, Oct 10, 2013 at 9:46 PM, SoundsFromSound soundsfromso...@gmail.comwrote: Hi Gabe, Welcome to LilyPond! If you'd like to put a note in parenthesis, simply add this command: \parenthesize ...to whichever pitches you which to enclose. http://www.lilypond.org/doc/v2.16/Documentation/notation/inside-the-staff#parentheses If you want to put simple text/characters below a note, just use this: _ your text here or characters (underscore and then your text in quotes) http://www.lilypond.org/doc/v2.16/Documentation/notation/writing-text Hope this helps, Ben Gabe Moothart wrote Hello! I am new to lilypond, and I'm trying to layout a psalm chanted in plainsong, so that the output should look something like this: https://dl.dropboxusercontent.com/u/84432/psalm_example.png So far I have this: https://gist.github.com/gmoothart/6929479 which renders like so: https://dl.dropboxusercontent.com/u/84432/ps149.pdf Any comments/suggestions are helpful, but I think my biggest questions are: 1) How to create the bar in the music (I've inserted rests just to show where they go) ? 2) How to add parentheses around the optional notes, as in the example 3) How to add markings directly below the music (the ticks and slashes in the example) 4) how to add an umlaut over a letter as in the example. Thanks in advance for any help. So far I'm very impressed with lilypond! Gabe ___ lilypond-user mailing list lilypond-user@ https://lists.gnu.org/mailman/listinfo/lilypond-user - composer | sound designer LilyPond Tutorials (for beginners) -- http://bit.ly/bcl-lilypond -- View this message in context: http://lilypond.1069038.n5.nabble.com/laying-out-plainsong-chant-tp152101p152102.html Sent from the User mailing list archive at Nabble.com. ___ 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: Stand alone guitar chord diagrams
Kevin Tough wrote First thanks for the help getting started with Lilypond! In my course documentation I will need a flexible means to generate chord diagrams. I would be greatly surprised that Lilypond could be used for this but perhaps someone has experience with this and would make a suggestion as to what I might use. I'm running Linux and would prefer something open source. well, if you'd give us some more details or examples, we could try an attempt!? Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Stand-alone-guitar-chord-diagrams-tp152190p152206.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ugly bar line when changing line-count
Hi Elize, Thank you very much for your answer. I had a look on your code, and here is what I think about these issues: - indeed most of these things are easily corrected with some sort of tweaking, but I believe that (at least some of them) should be automatic. Let's go case by case. - I already spoke about the issue in the first example in your code named corrected bar-line. I still believe that the bar line should cover all five lines (or the largest number of lines, such as in this code: barlines.ly http://lilypond.1069038.n5.nabble.com/file/n152207/barlines.ly http://lilypond.1069038.n5.nabble.com/file/n152207/barlines.png - In your second example adding a time signature, you seem to have missed my point. I am able to add a time signature, the problem is that the time signature makes a mess with the line-count. Have a look on your own example, note that the 3/4 is in between a clash of the old 5 lines against the new 2 lines. This looks just plain wrong and it shouldn't behave like this. In my opinion, this is clearly a bug. Here is an image: http://lilypond.1069038.n5.nabble.com/file/n152207/timesig.png - 3rd example: no problems here; as I mentioned before, accidentals do not cause any problem unless the line-count happens in the middle of a measure, like your last example. - Finally, the last example with accidentals inside the measure requires a kind of a hack by using the \bar . It works well, but my point is: why would the automatic case leave the accidental in the previous line-count, when this behavior is clearly not desirable? Would anyone really wish to have the accidentals printed in a different line-count? Thank you once again for your help and your comments, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/ugly-bar-line-when-changing-line-count-tp152072p152207.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Flat flags
Perfect Harm, thanks a lot! I am really looking forward to it. Take care, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/Flat-flags-tp151684p152208.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ugly bar line when changing line-count
Gilberto Agostinho wrote - I already spoke about the issue in the first example in your code named corrected bar-line. I still believe that the bar line should cover all five lines (or the largest number of lines, such as in this code: there are more options to do this, eg. \once \override Staff.StaffSymbol.layer = 3 - In your second example adding a time signature, you seem to have missed my point. I am able to add a time signature, the problem is that the time signature makes a mess with the line-count. Have a look on your own example, note that the 3/4 is in between a clash of the old 5 lines against the new 2 lines. This looks just plain wrong and it shouldn't behave like this. In my opinion, this is clearly a bug. Here is an image: there's no mess - you want a staff with an even number of staff lines against an odd number before - this must be dis-/mis-located. having the staff lines dislocated by half a staff doesn't make sense to me (how would you play or read this for a melodic instrument?) obviously LP draws the staff line from one bar to the next (which I consider reasonable) and when there's a time or key change this is displayed before the staff stops. - 3rd example: no problems here; as I mentioned before, accidentals do not cause any problem unless the line-count happens in the middle of a measure, like your last example. not sure it's *my* example - Finally, the last example with accidentals inside the measure requires a kind of a hack by using the \bar . It works well, but my point is: why would the automatic case leave the accidental in the previous line-count, when this behavior is clearly not desirable? Would anyone really wish to have the accidentals printed in a different line-count? why should it not leave the accidental in its natural place which is determined by certain horizontal spacing rules (which are well documented in the docs, imo)? if you think there should be other rules for all this, would you like to try to gather them in a - maybe - simple (scheme-) function?! Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/ugly-bar-line-when-changing-line-count-tp152072p152213.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to print just a tempo in a LaTeX document?
Just to bring this thread to a conclusion:
After two weeks of part-time effort to upgrade from Debian sneezey to
wheezy (or something like that), I still ended up with just lilypond
2.14.2, which didn't work with either of David's examples. Next attempt
will be to dump the Debian install of lilypond and roll my own.
However, I did discover this thread:
http://tex.stackexchange.com/questions/68461/searching-a-musical-quarter-note-symbol-to-insert-into-text
which does exactly what I want. I put this section into the preamble of
my .lytex document:
% For quarternote in tempo line:
\providecommand*{\quarternote}{%
\begingroup
\fontencoding{U}%
\fontfamily{wasy}%
\selectfont
\symbol{12}%
\endgroup
}
and put this in the /begin{document} ... /end{document} section:
{\LARGE \quarternote}~= 90
Thanks, again, for everyone's suggestions.
-Kevin
On Fri, 2013-10-04 at 14:58 +0200, David Kastrup wrote:
Kevin Zembower kzembo...@verizon.net writes:
On Fri, 2013-10-04 at 07:53 +0200, David Kastrup wrote:
For me,
\lilypond[quote]{\new Lyrics \tempo 4 = 90}
works just fine, but requires at least version 2.17.8, exactly because
of that score with no music issue.
You can probably do
\begin{lilypond}
\new Lyrics { \tempo 4 = 90 }
\end{lilypond}
David, thanks for your suggestion. I have lilypond 2.12.3, which doesn't
work with your second suggestion:
Parsing...
musicSheet.lytex:35:31: error: syntax error, unexpected STRING
\new Lyrics { \tempo 4 = 90
}
Uh, I have no idea why it would work with mine, actually. This would
have to be
\new Lyrics \lyricsmode { \tempo 4 = 90 }
Version 2.12.3 is the version available with Debian squeeze 6.0.7. I try
not to install individual packages, and prefer to do it through the
package management system, so that I get updates, especially security
updates, automatically. However, your suggestion caused me to notice
that Debian is now up to 7.1, so I may update and see what version of
lilypond that gives me.
2.14 has been released in 2011, more than 2 years ago. 2.16 is already
more than one year old. 2.12 has last been updated in 2009 (if we are
discounting the update of the Japanese translation).
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ugly bar line when changing line-count
Hi Elize, Thanks again for your reply. First of all, let me just make some things clear: I am not a programmer by any means, I am just a musician. My motivation to write to this mailing list is to help to improve LilyPond; thus, when I see something that seems odd according to what I believe are the notation standards, I feel that I should point out here. That said, here are my thoughts on your message: Eluze wrote there are more options to do this, eg. \once \override Staff.StaffSymbol.layer = 3 I will experiment with these and other options. But as I wrote before, I was recommending that LilyPond would behave like I proposed /automatically/. So I am not really looking for some tweak or workaround here (I am not actually writing any music right now that needs these things). I was simply pointing out how I think bar lines are notated when a change of number of lines happen. People are welcome to agree or disagree with me, as well as implement or reject my ideas. Eluze wrote there's no mess - you want a staff with an even number of staff lines against an odd number before - this must be dis-/mis-located. Yes, this is correct. However, this was never pointed out as a problem by me. Eluze wrote having the staff lines dislocated by half a staff doesn't make sense to me (how would you play or read this for a melodic instrument?) To me it does make sense that the lines are dislocated when changing from an odd no of lines to an even no of lines, or vice-versa. And about using this for a melodic instrument, I agree with you that this would be of no use, but when using a mix of pitched and unpitched percussion, this kind of notation might appear in the full score of an orchestral work if the composer decides to notate one staff per percussion player (instead of per instrument), for instance. Here is a silly small example of what I have already came across: percussion.ly http://lilypond.1069038.n5.nabble.com/file/n152215/percussion.ly http://lilypond.1069038.n5.nabble.com/file/n152215/percussion.png Eluze wrote obviously LP draws the staff line from one bar to the next (which I consider reasonable) and when there's a time or key change this is displayed before the staff stops. Please have a look on the image below. The top time signatures are the automatic ones generated via LP. The bottom ones are retouched images of what I think it would look better. I don't know how LP works on this regard, I am simply pointing out that those lines crossing over the time signature are not part of any standard of notation. http://lilypond.1069038.n5.nabble.com/file/n152215/timesig2.png Eluze wrote not sure it's *my* example Well, I meant the code you attached. The last item/example/staff of the code you attached. Eluze wrote why should it not leave the accidental in its natural place which is determined by certain horizontal spacing rules (which are well documented in the docs, imo)? I am not arguing about changing the position of any accidentals! I am arguing that the no. of staff lines should be changed before the accidental. http://lilypond.1069038.n5.nabble.com/file/n152215/accidentals.png Eluze wrote if you think there should be other rules for all this, would you like to try to gather them in a - maybe - simple (scheme-) function?! I can certainly try to create a function that deals with these issues myself, but I don't see much reason for this. First of all, I am not very familiar with LP's functions and it would take me a while to learn it. Secondly, I don't see why they would be useful in this case. I am basically arguing that LP should behave like this and that *out of the box*, due to what are the standards of notation IMO. Thanks once again for your replies. Take care, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/ugly-bar-line-when-changing-line-count-tp152072p152215.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics to hymn - new user
On Sat, Oct 12, 2013 at 9:26 PM, Garrett McGilvray
garrett.mcgilv...@gmail.com wrote:
Hi folks,
The short version of the question (I think) is this: how do you set a
multi-measure rest when manually specifying lyric duration?
--
If the short version isn't sufficient, here is what I am trying to solve:
I've hit a brick wall trying to figure out how to layout my lyrics for a
hymn. The arrangement is fairly common, where everyone sings the same line
for each of the stanzas, but there are split parts in the chorus. I
attached a picture of the hymn so you can see what I mean more clearly:
I had in mind setting almost all of the lyrics to the women voice
(soprano alto), and then manually entering the duration for only the
lower part of the chorus (where the basses start their soli in the chorus).
However, that's the part where I would need to know how to put a
multi-measure rest so that that line won't begin during the verses. Or is
there a better way?
I have a template I use for my hymn writing that allows me to deal with
this fairly easily, but it relies in part on a hacked version of LilyPond.
The basic answer is that you ideally need two sequential sets of voice
contexts, one for the verse, one for the chorus. So this would be your
basic setup:
\score {
\new Staff = top {
\new Voice = sopVerse { } % voice for verse melody and combined
alto
\new Voice = altoVerse { } % voice for verse alto lines that
require separate stem, such as days on line 2
\new Voice = sopChorus { } % voice for chorus melody and combined
alto
\new Voice = altoChorus { } % voice for chorus alto lines that
require separate stem, particularly gently home at end
}
\new Staff = bottom {
\new Voice = tenVerse { } % voice for verse tenor lines requiring
separate stems
\new Voice = bassVerse { } % voice for verse bass and combined
tenor stems
\new Voice = tenChorus { } % voice for chorus tenor lines
requiring separate stems
\new Voice = bassChorus { } % voice for chorus bass and combined
tenor stems
}
}
You'll then associate your lyrics with the proper voices. Since the tenor
requires no separate lyrics (the final gently home can be attached to the
altoChorus voice), the mmr is not a huge issue here. You may need to do
some manual positioning to put it up high enough.
Cheers,
Carl
P.S.: nice scan from Wiegand's _Praise for the Lord_
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Complete syntax documentation
Hi Kevin, The LilyPond documentation goes into detail about concepts like simultaneous notes, music expressions (braces), etc. - have you checked this page out yet? -- http://www.lilypond.org/doc/v2.17/Documentation/notation/musical-notation Each sub-link on that notation page has topics mapped out piece by piece, and it sounds like that is exactly what you are looking for. Ben Kevin wrote I have searched and searched, but I can't to seem find any documentation on the actual file structure, with all the various elements, in one place. Yes, I can find out about how curly braces work, or what does, but it would be great if there was a document that listed each delimiter, what it does, and how it interacts with other delimiters. Thanks, Kevin ___ lilypond-user mailing list lilypond-user@ https://lists.gnu.org/mailman/listinfo/lilypond-user - composer | sound designer LilyPond Tutorials (for beginners) -- http://bit.ly/bcl-lilypond -- View this message in context: http://lilypond.1069038.n5.nabble.com/Complete-syntax-documentation-tp139619p152219.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: laying out plainsong chant
Joram,
Thanks. I noticed that in the feta font there are different rest glyphs:
(
http://www.lilypond.org/doc/v2.17/Documentation/notation/the-feta-font#rest-glyphs
)
And I guess lilypond is automatically choosing one for the even staff lines
(rests.1), and the other for odd lines (rests.1o). Is it maybe possible to
override the glyph the same way you overrode the other properties?
TIA,
Gabe
On Sat, Oct 12, 2013 at 1:12 PM, Noeck noeck.marb...@gmx.de wrote:
Hi Gabe,
please always reply to the list, because others might also be interested
and in this case I can't help much.
Here is a parametrized version of \longbar which puts it on the line
number pos. However with odd numbers, ledger lines are drawn for the
rest and it looks different. I don't know how to handle this.
The optimal function could be used in this way:
a\longbar instead of \longbar -2
But I don't know how to do that.
Cheers,
Joram
\version 2.17.26
longbar = #(define-music-function (parser location pos) (number?)
#{
\override Rest #'font-size = #4
\override Rest #'staff-position = #pos
r2*1/4
\once \override Rest #'extra-offset = #'(-1.3 . 0)
r2*1/4
\revert Rest #'font-size
\revert Rest #'staff-position
#})
%usage (example)
{
\cadenzaOn
r4 \longbar -2 \longbar 2 \longbar 1 r4
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
