mpdolce - LilyPond

More documents

Recommendations

Info

Chapter 2: Tutorial 12 For future use of LilyPond, you should begin by selecting ‘New’ or ‘Open’. You must save your file before typesetting it. If any errors occur in processing, please see the log window. Windows On Windows, if you double-click in the LilyPond icon on the Desktop, it will open a simple text editor with an example file. Save it, for example, to ‘test.ly’ on your Desktop and then double-click on the file to process it (the file icon looks like a note). After some seconds, you will get a file ‘test.pdf’ on your desktop. Double-click on this PDF file to view the typeset score. An alternative method to process the ‘test.ly’ file is to drag and drop it onto the LilyPond icon using your mouse pointer. To edit an existing ‘.ly’ file, right-click on it and select “Edit source”. To get an empty file to start from, run the editor as described above and use “New” in the “File” menu, or right-click on the desktop and select “New..Text Document”, change its name to a name of your choice and change the file extension to .ly. Double-click the icon to type in your LilyPond source code as before. Double-clicking the file does not only result in a PDF file, but also produces a ‘.log’ file that contains some information on what LilyPond has done to the file. If any errors occur, please examine this file. UNIX Create a text file called ‘test.ly’ and enter: { c' e' g' e' } To process ‘test.ly’, proceed as follows: lilypond test.ly You will see something resembling: lilypond test.ly GNU LilyPond 2.12.3 Processing `test.ly' Parsing... Interpreting music... Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `test.ps'... Converting to `test.pdf'... 2.1.2 Simple notation LilyPond will add some notation elements automatically. In the next example, we have only specified four pitches, but LilyPond has added a clef, time signature, and rhythms. { c' e' g' e' } � � � � � �
Chapter 2: Tutorial 13 This behavior may be altered, but in most cases these automatic values are useful. Pitches Music Glossary: Section “pitch” in Music Glossary, Section “interval” in Music Glossary, Section “scale” in Music Glossary, Section “middle C” in Music Glossary, Section “octave” in Music Glossary, Section “accidental” in Music Glossary. The easiest way to enter notes is by using \relative mode. In this mode, the octave is chosen automatically by assuming the following note is always to be placed closest to the previous note, i.e., it is to be placed in the octave which is within three staff spaces of the previous note. We begin by entering the most elementary piece of music, a scale, in which every note is within just one staff space of the previous note. % set the starting point to middle C \relative c' { c d e f g a b c } � � � � � � � � � � The initial note is middle C. Each successive note is placed closest to the previous note – in other words, the first c is the closest C to middle C. This is followed by the closest D to the previous note. We can create melodies which have larger intervals, still using only \relative mode: \relative c' { d f a g c b f d } � � � � � � � � � � It is not necessary for the first note of the melody to start on the note which specifies the starting pitch. In the previous example, the first note – the d – is the closest D to middle C. By adding (or removing) quotes ' or commas , from the \relative c' { command, we can change the starting octave: % one octave above middle C \relative c'' { e c a c } � � � � � � Relative mode can be confusing initially, but is the easiest way to enter most melodies. Let us see how this relative calculation works in practice. Starting from a B, which is on the middle line in a treble clef, you can reach a C, D and E within 3 staff spaces going up, and an A, G and F within 3 staff spaces going down. So if the note following a B is a C, D or E it will be assumed to be above the B, and an A, G or F will be assumed to be below.
Page 1 and 2: LilyPond Learning Manual The LilyPo
Page 3 and 4: 3 Fundamental concepts . . . . . .
Page 5 and 6: Preface 1 Preface It must have been
Page 7 and 8: Chapter 1: Introduction 3 � �
Page 9 and 10: Chapter 1: Introduction 5 How can w
Page 11 and 12: Chapter 1: Introduction 7 This expr
Page 13 and 14: Chapter 1: Introduction 9 About the
Page 15: Chapter 2: Tutorial 11 2 Tutorial T
Page 19 and 20: Chapter 2: Tutorial 15 3 � �
Page 21 and 22: Chapter 2: Tutorial 17 parentheses
Page 23 and 24: Chapter 2: Tutorial 19 LilyPond mak
Page 25 and 26: Chapter 2: Tutorial 21 Fingerings M
Page 27 and 28: Chapter 2: Tutorial 23 See also Not
Page 29 and 30: Chapter 2: Tutorial 25 Simultaneous
Page 31 and 32: Chapter 2: Tutorial 27 \new Staff .
Page 33 and 34: Chapter 2: Tutorial 29 2.4.2 Aligni
Page 35 and 36: Chapter 2: Tutorial 31 3 � �
Page 37 and 38: Chapter 2: Tutorial 33 � � 8 6
Page 39 and 40: Chapter 2: Tutorial 35 \version "2.
Page 41 and 42: Chapter 3: Fundamental concepts 37
Page 67 and 68:
Chapter 3: Fundamental concepts 63
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Chapter 4: Tweaking output 81 in in
Page 87 and 88:
Chapter 4: Tweaking output 83 There
Page 89 and 90:
Chapter 4: Tweaking output 85 that
Page 91 and 92:
Chapter 4: Tweaking output 87 Overr
Page 93 and 94:
Chapter 4: Tweaking output 89 You w
Page 95 and 96:
Chapter 4: Tweaking output 91 4.3 A
Page 97 and 98:
Chapter 4: Tweaking output 93 �
Page 99 and 100:
Chapter 4: Tweaking output 95 Note
Page 101 and 102:
Page 103 and 104:
Chapter 4: Tweaking output 99 the t
Page 105 and 106:
Chapter 4: Tweaking output 101 \dot
Page 107 and 108:
Chapter 4: Tweaking output 103 < c
Page 109 and 110:
Chapter 4: Tweaking output 105 prio
Page 111 and 112:
Chapter 4: Tweaking output 107 c,,2
Page 113 and 114:
Chapter 4: Tweaking output 109 4.5
Page 115 and 116:
Chapter 4: Tweaking output 111 posi
Page 117 and 118:
Chapter 4: Tweaking output 113 staf
Page 119 and 120:
Chapter 4: Tweaking output 115 r4 \
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Chapter 4: Tweaking output 121 } g2
Page 127 and 128:
Chapter 4: Tweaking output 123 } c4
Page 129 and 130:
Chapter 4: Tweaking output 125 Simu
Page 131 and 132:
Chapter 4: Tweaking output 127 } \n
Page 133 and 134:
Chapter 4: Tweaking output 129 \ove
Page 135 and 136:
Chapter 5: Working on LilyPond proj
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Appendix A: Templates 141 Appendix
Page 147 and 148:
Appendix A: Templates 143 A.1.4 Not
Page 149 and 150:
Appendix A: Templates 145 } \key c
Page 151 and 152:
Appendix A: Templates 147 } dynamic
Page 153 and 154:
Appendix A: Templates 149 cello = \
Page 155 and 156:
Appendix A: Templates 151 %{ Uncomm
Page 157 and 158:
Appendix A: Templates 153 } \new St
Page 159 and 160:
Appendix A: Templates 155 } \new Vo
Page 161 and 162:
Appendix A: Templates 157 } \score
Page 163 and 164:
Appendix A: Templates 159 discantus
Page 165 and 166:
Appendix A: Templates 161 bassusNot
Page 167 and 168:
Appendix A: Templates 163 3 � �
Page 169 and 170:
Appendix A: Templates 165 global =
Page 171 and 172:
Appendix A: Templates 167 \voiceOne
Page 173 and 174:
Appendix A: Templates 169 } >> \lay
Page 175 and 176:
Appendix A: Templates 171 \begin{li
Page 177 and 178:
Appendix B: Scheme tutorial 173 App
Page 179 and 180:
Appendix B: Scheme tutorial 175 TOD
Page 181 and 182:
Appendix C: GNU Free Documentation
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Appendix D: LilyPond index 183 \sto
Page 189 and 190:
Appendix D: LilyPond index 185 H ha
Page 191 and 192:
Appendix D: LilyPond index 187 rest
show all

mpdolce - LilyPond

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?