mpdolce - LilyPond

More documents

Recommendations

Info

Chapter 4: Tweaking output 100 } >> � � � � � � � � 4.4.2 Within-staff objects We have already seen how the commands \voiceXXX affect the direction of slurs, ties, fingering and everything else which depends on the direction of the stems. These commands are essential when writing polyphonic music to permit interweaving melodic lines to be distinguished. But occasionally it may be necessary to override this automatic behavior. This can be done for whole sections of music or even for an individual note. The property which controls this behavior is the direction property of each layout object. We first explain what this does, and then introduce a number of ready-made commands which avoid your having to code explicit overrides for the more common modifications. Some layout objects like slurs and ties curve, bend or point either up or down; others like stems and flags also move to right or left when they point up or down. This is controlled automatically when direction is set. The following example shows in bar 1 the default behavior of stems, with those on high notes pointing down and those on low notes pointing up, followed by four notes with all stems forced down, four notes with all stems forced up, and finally four notes reverted back to the default behavior. a4 g c a \override Stem #'direction = #DOWN a g c a \override Stem #'direction = #UP a g c a \revert Stem #'direction a g c a � � � � � � � � � � � � � � � � � � Here we use the constants DOWN and UP. These have the values -1 and +1 respectively, and these numerical values may be used instead. The value 0 may also be used in some cases. It is simply treated as meaning UP for stems, but for some objects it means ‘center’. There is a constant, CENTER which has the value 0. However, these explicit overrides are not usually used, as there are simpler equivalent predefined commands available. Here is a table of the commonest. The meaning of each is stated where it is not obvious. Down/Left Up/Right Revert Effect \arpeggioArrowDown\arpeggioArrowUp\arpeggioNormal Arrow is at bottom, at top, or no arrow
Chapter 4: Tweaking output 101 \dotsDown \dotsUp \dotsNeutral Direction of movement to avoid staff lines \dynamicDown \dynamicUp \dynamicNeutral \phrasingSlurDown \phrasingSlurUp \phrasingSlurNeutralNote: distinct from slur commands \slurDown \slurUp \slurNeutral \stemDown \stemUp \stemNeutral \textSpannerDown \textSpannerUp \textSpannerNeutral Text entered as spanner is below/above staff \tieDown \tieUp \tieNeutral \tupletDown \tupletUp \tupletNeutral Tuplets are below/above notes Note that these predefined commands may not be preceded by \once. If you wish to limit the effect to a single note you must either use the equivalent \once \override command or use the predefined command followed after the affected note by the corresponding \xxxNeutral command. Fingering The placement of fingering on single notes can also be controlled by the direction property, but changing direction has no effect on chords. As we shall see, there are special commands which allow the fingering of individual notes of chords to be controlled, with the fingering being placed above, below, to the left or to the right of each note. First, here’s the effect of direction on the fingering attached to single notes. The first bar shows the default behaviour, and the following two bars shows the effect of specifying DOWN and UP: c-5 a-3 f-1 c'-5 \override Fingering #'direction = #DOWN c-5 a-3 f-1 c'-5 \override Fingering #'direction = #UP c-5 a-3 f-1 c'-5 � � 5 � 3 1 5 � � � � � � 5 3 1 � 5 5 3 1 � � However, overriding the direction property is not the easiest way of manually setting the fingering above or below the notes; using _ or ^ instead of - before the fingering number is usually preferable. Here is the previous example using this method: c-5 a-3 f-1 c'-5 c_5 a_3 f_1 c'_5 c^5 a^3 f^1 c'^5 � � 5 3 1 5 5 3 � � � � � 5 � 3 � 1 � 5 � � The direction property is ignored for chords, but the directional prefixes, _ and ^ do work. By default, the fingering is automatically placed both above and below the notes of a chord, as shown: � 1 � 5 � 5 �
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 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54: Chapter 3: Fundamental concepts 49
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 103: Chapter 4: Tweaking output 99 the t
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 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 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?