mpdolce - LilyPond

More documents

Recommendations

Info

Chapter 3: Fundamental concepts 62 Rest engraver Engraves rests Staff symbol engraver Engraves the five (by default) lines of the staff Stem engraver Creates stems and single-stem tremolos Time signature engraver Creates time signatures We shall see later how the output of LilyPond can be changed by modifying the action of Engravers. See also Internals reference: Section “Engravers and Performers” in Internals Reference. 3.3.4 Modifying context properties Contexts are responsible for holding the values of a number of context properties. Many of them can be changed to influence the interpretation of the input and so change the appearance of the output. They are changed by the \set command. This takes the form \set ContextName.propertyName = #value Where the ContextName is usually Score, Staff or Voice. It may be omitted, in which case Voice is assumed. The names of context properties consist of words joined together with no hyphens or underscores, all except the first having a capital letter. Here are a few examples of some commonly used ones. There are many more. propertyName Type Function Example Value extraNatural Boolean If true, set extra natural signs before accidentals #t, #f currentBarNumber Integer Set the current bar number 50 doubleSlurs Boolean If true, print slurs both above and below notes #t, #f instrumentName Text Set the name to be placed at the start of the staff "Cello I" fontSize Real Increase or decrease the font size 2.4 stanza Text Set the text to print before the start of a verse "2" where a Boolean is either True (#t) or False (#f), an Integer is a positive whole number, a Real is a positive or negative decimal number, and text is enclosed in double apostrophes. Note the occurrence of hash signs, (#), in two different places – as part of the Boolean value before the t or f, and before value in the \set statement. So when a Boolean is being entered you need to code two hash signs, e.g., ##t. Before we can set any of these properties we need to know in which context they operate. Sometimes this is obvious, but occasionally it can be tricky. If the wrong context is specified, no error message is produced, but the expected action will not take place. For example, the instrumentName clearly lives in the Staff context, since it is the staff that is to be named. In this example the first staff is labelled, but not the second, because we omitted the context name.
Chapter 3: Fundamental concepts 63 \new Staff \relative c' { \set instrumentName = #"Alto" % Wrong! d4 d } >> Soprano � � � � � � � � Remember the default context name is Voice, so the second \set command set the property instrumentName in the Voice context to “Alto”, but as LilyPond does not look for any such property in the Voice context, no further action took place. This is not an error, and no error message is logged in the log file. Similarly, if the property name is mis-spelt no error message is produced, and clearly the expected action cannot be performed. In fact, you can set any (fictitious) ‘property’ using any name you like in any context that exists by using the \set command. But if the name is not known to LilyPond it will not cause any action to be taken. Some text editors with special support for LilyPond input files document property names with bullets when you hover them with the mouse, like JEdit with LilyPondTool, or highlight unknown property names differently, like ConTEXT. If you do not use an editor with such features, it is recommended to check the property name in the Internals Reference: see Section “Tunable context properties” in Internals Reference, or Section “Contexts” in Internals Reference. The instrumentName property will take effect only if it is set in the Staff context, but some properties can be set in more than one context. For example, the property extraNatural is by default set to ##t (true) for all staves. If it is set to ##f (false) in one particular Staff context it applies just to the accidentals on that staff. If it is set to false in the Score context it applies to all staves. So this turns off extra naturals in one staff: > � � �� and this turns them off in all staves:
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 and 16: Chapter 2: Tutorial 11 2 Tutorial T
Page 17 and 18: Chapter 2: Tutorial 13 This behavio
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 65: Chapter 3: Fundamental concepts 61
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: Chapter 4: Tweaking output 97 �
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:
Chapter 4: Tweaking output 117 �
Page 123 and 124:
Chapter 4: Tweaking output 119 �
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?