@itemize @bullet
@item Include @code{\version} numbers in every file. Note that all
-templates contain a @code{\version "2.6.0"} string. We
+templates contain a @code{\version "2.7.32"} 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
of the music. For very simple music, perhaps just once or twice. For
very complex music, every bar.
-@item One bar per line. If there is anything complicated, either in the music
+@item One bar per line of text. If there is anything complicated, either in the music
itself or in the output you desire, it's often good to write only one bar
per line. Saving screen space by cramming eight bars per line just isn't
worth it if you have to `debug' your files.
@end itemize
+If you are entering music from an existing score (ie typesetting a
+piece of existing sheet music),
+
+@itemize @bullet
+
+@item Enter one manuscript (the physical copy) system at a time (but still
+only one bar per line of text), and
+check each system when you finish it. You may use the
+@code{showLastLength} command to speed up processing -- see
+@ref{Skipping corrected music}.
+
+@item Define @code{mBreak = @{ \break @}} and insert @code{\mBreak}
+in the input file whenever the manuscript has a line break. This
+makes it much easier to compare the LilyPond music to the original
+music. When you are finished proofreading your score, you may
+define @code{mBreak = @{ @}} to remove all those line breaks. This
+will allow LilyPond to place line breaks wherever it feels are
+best.
+
+@end itemize
+
@node Extending the templates
@section Extending the templates
soprano part).
@example
-\version "2.6.0"
+\version "2.7.39"
melody = \relative c' @{
\clef treble
\key c \major
\score@{
<<
- \context Voice = one @{
+ \new Voice = "one" @{
\autoBeamOff
\melody
@}
- \lyricsto "one" \new Lyrics \text
+ \new Lyrics \lyricsto "one" \text
>>
\layout @{ @}
\midi @{ \tempo 4=60 @}
Now we want to add a cello part. Let's look at the ``Notes only'' example:
@example
-\version "2.6.0"
+\version "2.7.39"
melody = \relative c' @{
\clef treble
\key c \major
notes.
@example
-\version "2.6.0"
+\version "2.7.39"
sopranoMusic = \relative c' @{
\clef treble
\key c \major
\score@{
<<
- \context Voice = one @{
+ \new Voice = "one" @{
\autoBeamOff
\sopranoMusic
@}
- \lyricsto "one" \new Lyrics \sopranoLyrics
+ \new Lyrics \lyricsto "one" \sopranoLyrics
>>
\layout @{ @}
\midi @{ \tempo 4=60 @}
@example
\score@{
-<<
<<
- \context Voice = one @{
- \autoBeamOff
- \sopranoMusic
- @}
- \lyricsto "one" \new Lyrics \sopranoLyrics
+ <<
+ \new Voice = "one" @{
+ \autoBeamOff
+ \sopranoMusic
+ @}
+ \new Lyrics \lyricsto "one" \sopranoLyrics
+ >>
+ \new Staff \celloMusic
>>
- \new Staff \celloMusic
->>
\layout @{ @}
\midi @{ \tempo 4=60 @}
@}
This looks a bit messy; the indentation is messed up now. That is
easily fixed. Here's the complete soprano and cello template.
-@lilypond[quote,verbatim,raggedright]
-\version "2.6.0"
+@lilypond[quote,verbatim,ragged-right]
+\version "2.7.39"
sopranoMusic = \relative c' {
\clef treble
\key c \major
\score{
<<
- <<
- \context Voice = one {
- \autoBeamOff
- \sopranoMusic
- }
- \lyricsto "one" \new Lyrics \sopranoLyrics
- >>
- \new Staff \celloMusic
+ <<
+ \new Voice = "one" {
+ \autoBeamOff
+ \sopranoMusic
+ }
+ \new Lyrics \lyricsto "one" \sopranoLyrics
+ >>
+ \new Staff \celloMusic
>>
\layout { }
\midi { \tempo 4=60 }
elements can overlap. This is unfortunate, but (in most cases) is easily
solved.
-@lilypond[quote,fragment,raggedright,verbatim,relative=2]
+@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
e4^\markup{ \italic ritenuto } g b e
@end lilypond
The easiest solution is to increase the distance between the object
(in this case text, but it could easily be fingerings or dynamics
instead) and the note. In LilyPond, this is called the
-@code{padding} property. For most objects, it is around 1.0 or
-less (it varies with each object). We want to increase it, so let's
-try 1.5
+@code{padding} property; it is measured in staff spaces. For most
+objects, this value is around 1.0 or less (it varies with each
+object). We want to increase it, so let's try 1.5
-@lilypond[quote,fragment,raggedright,verbatim,relative=2]
+@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
\once \override TextScript #'padding = #1.5
e4^\markup{ \italic ritenuto } g b e
@end lilypond
the movement is done after LilyPond has placed all other objects. This means
that the result can overlap with other objects.
-@lilypond[quote,fragment,raggedright,verbatim,relative=2]
+@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
\once \override TextScript #'extra-offset = #'( 1.0 . -1.0 )
e4^\markup{ \italic ritenuto } g b e
@end lilypond
movement (up is positive). After a bit of experimenting, we decided
that these values look good
-@lilypond[quote,fragment,raggedright,verbatim,relative=2]
+@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
\once \override TextScript #'extra-offset = #'( -1.6 . 1.0 )
e4^\markup{ \italic ritenuto } g b e
@end lilypond
compile the examples, but in most cases the output will
look very odd if you omit the @code{\relative c'}.
-@lilypond[quote,fragment,raggedright,verbatim]
+@lilypond[quote,fragment,ragged-right,verbatim]
\relative c'' {
c4 a b c
}
@end example
When LilyPond looks at this file, it takes the value of
-@code{melody} and inserts it whenever it sees
+@code{melody} (everything after the equals sign) and
+inserts it whenever it sees
@code{\melody}. There's nothing special about the
names -- it could be @code{melody}, @code{global},
@code{pianorighthand}, or @code{foofoobarbaz}. You
\score @{
@{
<<
- \context Staff = singer @{
- @}
- \context PianoStaff = piano @{
- @}
+ \new Staff = "singer" <<
+ >>
+ \new PianoStaff = piano <<
+ >>
>>
@}
\layout @{ @}
\score @{
@{
<<
- \context Staff = singer @{
- \context Voice = vocal @{ @}
- \lyricsto vocal \new Lyrics @{ @}
- @}
- \context PianoStaff = piano @{
- \context Staff = upper @{ @}
- \context Staff = lower @{ @}
- @}
+ \new Staff = "singer" <<
+ \new Voice = "vocal" @{ @}
+ >>
+ \new Lyrics \lyricsto vocal \new Lyrics @{ @}
+ \new PianoStaff = "piano" <<
+ \new Staff = "upper" @{ @}
+ \new Staff = "lower" @{ @}
+ >>
>>
@}
\layout @{ @}
staff (left hand).
At this stage, we could start filling in notes. Inside
-the curly braces next to @code{\context Voice = vocal},
+the curly braces next to @code{\new Voice = vocal},
we could start writing
@example
\score @{
@{
<<
- \context Staff = singer @{
- \context Voice = vocal @{ \melody @}
- \lyricsto vocal \new Lyrics @{ \text @}
- @}
- \context PianoStaff = piano @{
- \context Staff = upper @{ \upper @}
- \context Staff = lower @{ \lower @}
- @}
+ \new Staff = "singer" <<
+ \new Voice = "vocal" @{ \melody @}
+ >>
+ \new Lyrics \lyricsto vocal \new Lyrics @{ \text @}
+ \new PianoStaff = "piano" <<
+ \new Staff = "upper" @{ \upper @}
+ \new Staff = "lower" @{ \lower @}
+ >>
>>
@}
\layout @{ @}
@end example
@noindent
-Remember that you can use any names you like.
+Remember that you can use almost any name you like. The
+limitations on identifier names are detailed in
+@ref{File structure}.
When writing a @code{\score} section, or when reading
one, just take it slowly and carefully. Start with
you find the error, but in many cases you need to do some
investigation to determine the source of the problem.
-The most powerful tool for this purpose is the
-comment (@code{%} and @code{%@{ ... %@}}). If you don't
+The most powerful tools for this purpose are the
+single line comment (indicated by @code{%}) and the block
+comment (indicated by @code{%@{ ... %@}}). If you don't
know where a problem is, start commenting out huge portions
of your input file. After you comment out a section, try
compiling the file again. If it works, then the problem
-must exist in the portion you just commented. If it doens't
+must exist in the portion you just commented. If it doesn't
work, then keep on commenting out material until you have
something that works.
projects / lilypond.git / blobdiff