already set up for you. Just add notes, run LilyPond, and enjoy
beautiful printed scores!
-@c bad node name for ancient notation to avoid confict
+@c bad node name for ancient notation to avoid confict
@menu
* Suggestions for writing LilyPond files::
* Single staff::
@node Suggestions for writing LilyPond files
@section Suggestions for writing LilyPond files
-Now you're ready to begin writing bigger LilyPond files -- not just the
+Now you're ready to begin writing larger LilyPond files -- not just the
little examples in the tutorial, but whole pieces. But how should you
go about doing it?
-The best answer is ``however you want to do it''. As long as LilyPond
+The best answer is ``however you want to do it.'' As long as LilyPond
can understand your files and produces the output that you want, it
doesn't matter what your files look like. That said, sometimes we
make mistakes when writing files. If LilyPond can't understand your
files, or produces output that you don't like, how do you fix the
problem?
-Here are a few suggestions that can help you in avoiding or fixing
+Here are a few suggestions that can help you to avoid or fix
problems:
@itemize @bullet
@item Include @code{\version} numbers in every file. Note that all
-templates contain a @code{\version "2.3.22"} string. We
+templates contain a @code{\version "2.4.0"} string. We
highly recommend that you always include the @code{\version}, no matter
how small your file is. Speaking from personal experience, it's
quite frustrating to try to remember which version of LilyPond you were
using a few years ago. @code{convert-ly} requires you to declare
which version of LilyPond you used.
-@item Include checks: See @ref{Bar check} and @ref{Octave check}. If you
+@item Include checks: See @ref{Bar check} and @ref{Octave check}. If you
include checks every so often, then if you make a mistake, you can pinpoint
it quicker. How often is ``every so often''? It depends on the complexity
of the music. For very simple music, perhaps just once or twice. For
add notes, and you're finished!
@lilypond[quote,verbatim,raggedright]
-\version "2.3.22"
+\version "2.4.0"
melody = \relative c' {
\clef treble
\key c \major
line.
@lilypond[quote,verbatim,raggedright]
-\version "2.3.22"
+\version "2.4.0"
melody = \relative c' {
\clef treble
\key c \major
Want to prepare a lead sheet with a melody and chords? Look no further!
@lilypond[quote,verbatim,raggedright]
-\version "2.3.22"
-melody = \relative c' {
+\version "2.4.0"
+melody = \relative c' {
\clef treble
\key c \major
\time 4/4
>>
\layout{ }
- \midi { \tempo 4=60}
+ \midi { \tempo 4=60}
}
@end lilypond
This template allows you to prepare a song with melody, words, and chords.
@lilypond[quote,verbatim,raggedright]
-\version "2.3.22"
-melody = \relative c' {
+\version "2.4.0"
+melody = \relative c' {
\clef treble
\key c \major
\time 4/4
Here is a simple piano staff.
@lilypond[quote,verbatim,raggedright]
-\version "2.3.22"
+\version "2.4.0"
upper = \relative c'' {
\clef treble
\key c \major
piano accompaniment underneath.
@lilypond[quote,verbatim,raggedright]
-\version "2.3.22"
-melody = \relative c'' {
+\version "2.4.0"
+melody = \relative c'' {
\clef treble
\key c \major
\time 4/4
the lyrics between the piano staff (and omit the separate melody staff).
@lilypond[quote,verbatim,raggedright]
-\version "2.3.22"
+\version "2.4.0"
upper = \relative c'' {
\clef treble
\key c \major
tweaking yourself.
@lilypond[quote,verbatim,raggedright]
-\version "2.3.22"
+\version "2.4.0"
upper = \relative c'' {
\clef treble
\key c \major
a2 c
}
-dynamics = {
+dynamics = {
s2\fff\> s4
s\!\pp
}
-pedal = {
+pedal = {
s2\sustainDown s2\sustainUp
}
section for time and key signatures.
@lilypond[quote,verbatim,raggedright]
-\version "2.3.22"
+\version "2.4.0"
global = {
\time 4/4
\key c \major
always the same for all parts.
@lilypond[quote,verbatim,raggedright]
-\version "2.3.22"
+\version "2.4.0"
global = {
\key c \major
\time 4/4
@end lilypond
-@c bad node name to avoid node name confict
+@c bad node name to avoid node name confict
@node Ancient notation templates
@section Ancient notation templates
staves rather than on the staves.
@lilypond[quote,verbatim,linewidth=11.0\cm]
-\version "2.3.22"
+\version "2.4.0"
global = {
% incipit
\skip 1*5
- % last bar contains a brevis (i.e. spans 2 bars);
+ % last bar contains a brevis (i.e., spans 2 bars);
% therefore do not draw this particular bar
\cadenzaOn
\skip 1*2
@section Jazz combo
This is a much more complicated template, for a jazz ensemble. Note that all
-instruments are notated @code{\key c \major}. This refers to the key in
+instruments are notated in @code{\key c \major}. This refers to the key in
concert pitch; LilyPond will automatically transpose the key if the music
is within a @code{\transpose} section.
@c The `linewidth' argument is for the \header.
@lilypond[quote,verbatim,raggedright,linewidth]
-\version "2.3.22"
+\version "2.4.0"
\header {
title = "Song"
subtitle = "(tune)"
% ############ Horns ############
% ------ Trumpet ------
-trpt = \transpose c d \relative c'' {
+trpt = \transpose c d \relative c'' {
\Key
c1 c c
}
}
% ------ Trombone ------
-tbone = \relative c {
+tbone = \relative c {
\Key
c1 c c
}
% ############ Rhythm Section #############
% ------ Guitar ------
-gtr = \relative c'' {
+gtr = \relative c'' {
\Key
c1 \sl b4 b b b \nsl c1
}
This template displays all available headers. Some of them are only
used in the Mutopia project; they don't affect the printed output at
-all. They are used if you want the piece to be listed with different
+all. They are used if you want the piece to be listed with different
information in the Mutopia database than you wish to have printed on the
music. For example, Mutopia lists the composer of the famous D major
violin concerto as TchaikovskyPI, whereas perhaps you wish to print
@ The `linewidth' is for \header.
@lilypond[quote,verbatim,raggedright,linewidth]
-\version "2.3.22"
+\version "2.4.0"
\header {
dedication = "dedication"
title = "Title"
and a second one indicating a breath mark.
@lilypond[quote,verbatim,raggedright]
-barOne = { \once \override Staff.BarLine #'bar-size = #2
+barOne = { \once \override Staff.BarLine #'bar-size = #2
\bar "|" }
-barTwo = { \once \override Staff.BarLine #'extra-offset = #'(0 . 2)
- \once \override Staff.BarLine #'bar-size = #2
+barTwo = { \once \override Staff.BarLine #'extra-offset = #'(0 . 2)
+ \once \override Staff.BarLine #'bar-size = #2
\bar "|" }
chant = \relative c' {
\set Score.timing = ##f
- \override Staff.Stem #'transparent = ##t
+ \override Staff.Stem #'transparent = ##t
f4 a2 \barTwo
g4 a2 f2 \barOne
LilyPond, compared to graphical score editors: in LilyPond, you can
very easily reuse small segments of music without writing them out
completely. This template defines a large number of small segments
-(@code{taor, grip, thrd,} etc), which can be reused easily.
+(@code{taor}, @code{grip}, @code{thrd}, etc), which can be reused easily.
-TODO - replace Bagpipe template with Andrew McNabb's work?
+@c TODO - replace Bagpipe template with Andrew McNabb's work?
@lilypond[quote,verbatim]
taor = { \grace { g32[ d' g e'] } }
thrd = { \grace { g32[ d' c'] } }
birl = { \grace { g32[ a g] } }
gstd = { \grace { g'32[ d' g] } }
-fgg = { \grace { f32[ g'32] } }
+fgg = { \grace { f32[ g'32] } }
dblb = { \grace { g'32[ b d'] } }
dblc = { \grace { g'32[ c' d'] } }
dble = { \grace { g'32[ e' f'] } }
dblf = { \grace { g'32[ f' g'] } }
dblg = { \grace { g'32[ f'] } }
dbla = { \grace { a'32[ g'] } }
-lgg = { \grace { g32 } }
-lag = { \grace { a32 } }
+lgg = { \grace { g32 } }
+lag = { \grace { a32 } }
cg = { \grace { c'32 } }
eg = { \grace { e'32 } }
gg = { \grace { g'32 } }
\dblg g'4 a'8 \gg a'4. |
\thrd d'4.( d'4) \eg a8 |
\time 9/8
- \dble e'4 \lag e'8 \gg e'16[ d'8. e'8] \gg f'4 g'8 |
+ \dble e'4 \lag e'8 \gg e'16[ d'8. e'8] \gg f'4 g'8 |
\break
\time 6/8
\thrd d'4.( d'4) f'8 |
\break
- \dblg g'4 e'8( e'8) \dblf f'8.[ e'16] |
+ \dblg g'4 e'8( e'8) \dblf f'8.[ e'16] |
\thrd d'4.( d'4) \cg d'8 |
\gg c'4 e'8 \thrd d'4.( |
d'4.) \gdcg d'4.
@section Lilypond-book templates
These templates are for use with @code{lilypond-book}. If you're not familiar
-with this program, please refer to @ref{Integrating text and music}.
+with this program, please refer to @ref{LilyPond-book}.
@subsection LaTeX
@subsection Texinfo
-You can include LilyPond fragments in texinfo; in fact, this entire manual
-is written in texinfo.
+You can include LilyPond fragments in Texinfo; in fact, this entire manual
+is written in Texinfo.
@example
\input texinfo
a4 b c d
@@end lilypond
-More texinfo text
+More Texinfo text
@@lilypond[verbatim,fragment,raggedright]
d4 c b a
@@bye
@end example
-
projects / lilypond.git / blobdiff