LilyPond Beginnershandleiding

More documents

Recommendations

Info

Hoofdstuk 4: Tweaking output 114 \ottava #0 c,4 c c c | 8va Slower pp Text ff This example also shows how to create Text Spanners – text with extender lines above a section of music. The spanner extends from the \startTextSpan command to the \stopTextSpan command, and the format of the text is defined by the \override TextSpanner command. For more details see Sectie “Text spanners” in Notatie-handleiding. It also shows how ottava brackets are created. If the default values of outside-staff-priority do not give you the placing you want, the priority of any of the objects may be overridden. Suppose we would like the ottava bracket to be placed below the text spanner in the example above. All we need to do is to look up the priority of OttavaBracket in the IR or in the tables above, and reduce it to a value lower than that of a TextSpanner, remembering that OttavaBracket is created in the Staff context: % Set details for later Text Spanner \override TextSpanner.bound-details.left.text = \markup { \small \bold Slower } % Place dynamics above staff \dynamicUp % Place following Ottava Bracket below Text Spanners \once \override Staff.OttavaBracket.outside-staff-priority = #340 % Start Ottava Bracket \ottava #1 c'4 \startTextSpan % Add Dynamic Text c4\pp % Add Dynamic Line Spanner c4\< % Add Text Script c4^Text | c4 c % Add Dynamic Text c4\ff c \stopTextSpan | % Stop Ottava Bracket \ottava #0 c,4 c c c | Slower 8va pp Text ff Note that some of these objects, in particular bar numbers, metronome marks and rehearsal marks, live by default in the Score context, so be sure to use the correct context when these are being overriden.
Hoofdstuk 4: Tweaking output 115 Slurs by default are classed as within-staff objects, but they often appear above the staff if the notes to which they are attached are high on the staff. This can push outside-staff objects such as articulations too high, as the slur will be placed first. The avoid-slur property of the articulation can be set to 'inside to bring the articulation inside the slur, but the avoid-slur property is effective only if the outside-staff-priority is also set to #f. Alternatively, the outside-staff-priority of the slur can be set to a numerical value to cause it to be placed along with other outside-staff objects according to that value. Here’s an example showing the effect of the two methods: c4( c^\markup { \tiny \sharp } d4.) c8 | c4( \once \override TextScript.avoid-slur = #'inside \once \override TextScript.outside-staff-priority = ##f c4^\markup { \tiny \sharp } d4.) c8 | \once \override Slur.outside-staff-priority = #500 c4( c^\markup { \tiny \sharp } d4.) c8 | Changing the outside-staff-priority can also be used to control the vertical placement of individual objects, although the results may not always be desirable. Suppose we would like “Text3” to be placed above “Text4” in the example under Automatic behavior, above (see Sectie 4.4.1 [Automatic behavior], pagina 108). All we need to do is to look up the priority of TextScript in the IR or in the tables above, and increase the priority of “Text3” to a higher value: c2^"Text1" c2^"Text2" | \once \override TextScript.outside-staff-priority = #500 c2^"Text3" c2^"Text4" | Text3 Text2 Text1 Text4 This certainly lifts “Text3” above “Text4” but it also lifts it above “Text2”, and “Text4” now drops down. Perhaps this is not so good. What we would really like to do is to position all the annotation at the same distance above the staff. To do this, we clearly will need to space the notes out horizontally to make more room for the text. This is done using the textLengthOn command. The \textLengthOn command By default, text produced by markup takes up no horizontal space as far as laying out the music is concerned. The \textLengthOn command reverses this behavior, causing the notes to be spaced out as far as is necessary to accommodate the text: \textLengthOn % Cause notes to space out to accommodate text c2^"Text1" c2^"Text2" |
Page 1 and 2:
LilyPond Beginnershandleiding Het L
Page 3 and 4:
3.1.4 On the un-nestedness of brack
Page 5 and 6:
Hoofdstuk 1: Leerboek 1 1 Leerboek
Page 7 and 8:
Hoofdstuk 1: Leerboek 3 Uit de menu
Page 9 and 10:
Hoofdstuk 1: Leerboek 5 Stap 3. Bek
Page 11 and 12:
Hoofdstuk 1: Leerboek 7 Stap 1. Maa
Page 13 and 14:
Hoofdstuk 1: Leerboek 9 Stap 2a. Co
Page 15 and 16:
Hoofdstuk 1: Leerboek 11 Het PDF-be
Page 17 and 18:
Hoofdstuk 1: Leerboek 13 1.1.4 Comm
Page 19 and 20:
Hoofdstuk 1: Leerboek 15 Relatieve
Page 21 and 22:
Hoofdstuk 1: Leerboek 17 4 3
Page 23 and 24:
Hoofdstuk 1: Leerboek 19 • Uitdru
Page 25 and 26:
Hoofdstuk 1: Leerboek 21 • Voorda
Page 27 and 28:
Hoofdstuk 2: Algemene muzieknotatie
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Hoofdstuk 3: Fundamentele concepten
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68: Hoofdstuk 3: Fundamentele concepten
Page 93 and 94: Hoofdstuk 4: Tweaking output 89 The
Page 95 and 96: Hoofdstuk 4: Tweaking output 91 The
Page 97 and 98: Hoofdstuk 4: Tweaking output 93 Zie
Page 99 and 100: Hoofdstuk 4: Tweaking output 95 mak
Page 101 and 102: Hoofdstuk 4: Tweaking output 97 4.2
Page 103 and 104: Hoofdstuk 4: Tweaking output 99 Zie
Page 105 and 106: Hoofdstuk 4: Tweaking output 101 }
Page 109 and 110: Hoofdstuk 4: Tweaking output 105
Page 113 and 114: Hoofdstuk 4: Tweaking output 109 In
Page 115 and 116: Hoofdstuk 4: Tweaking output 111 \o
Page 117: Hoofdstuk 4: Tweaking output 113 5
Page 123 and 124: Hoofdstuk 4: Tweaking output 119 si
Page 125 and 126: Hoofdstuk 4: Tweaking output 121 b2
Page 127 and 128: Hoofdstuk 4: Tweaking output 123 st
Page 129 and 130: Hoofdstuk 4: Tweaking output 125 Th
Page 133 and 134: Hoofdstuk 4: Tweaking output 129 Th
Page 139 and 140: Hoofdstuk 4: Tweaking output 135 \s
Page 141 and 142: Hoofdstuk 4: Tweaking output 137 \s
Page 145 and 146: Hoofdstuk 4: Tweaking output 141 %%
Page 147 and 148: Hoofdstuk 4: Tweaking output 143 7)
Page 149 and 150: Appendix A: Templates 145 \melody }
Page 151 and 152: Appendix A: Templates 147 \score {
Page 153 and 154: Appendix A: Templates 149 } \layout
Page 155 and 156: Appendix A: Templates 151 %%%%% (Th
Page 157 and 158: Appendix A: Templates 153 Violin 1
Page 159 and 160: Appendix A: Templates 155 hi
Page 161 and 162: Appendix A: Templates 157
Page 163 and 164: Appendix A: Templates 159 altonotes
Page 165 and 166: Appendix A: Templates 161 } \clef "
Page 167 and 168: Appendix A: Templates 163 > % End S
Page 169 and 170:
Appendix A: Templates 165 dot = \ma
Page 171 and 172:
Appendix A: Templates 167 A.5 Orche
Page 173 and 174:
Appendix A: Templates 169 } \new St
Page 175 and 176:
Appendix A: Templates 171 } \overri
Page 177 and 178:
Appendix A: Templates 173 tenorNote
Page 179 and 180:
Appendix A: Templates 175 } } } Dis
Page 181 and 182:
Appendix A: Templates 177 \header {
Page 183 and 184:
Appendix A: Templates 179 } trombon
Page 185 and 186:
Appendix A: Templates 181 } down =
Page 187 and 188:
Appendix B: GNU Free Documentation
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Appendix C: LilyPond register 191 \
Page 197 and 198:
Appendix C: LilyPond register 193 L
Page 199:
Appendix C: LilyPond register 195 t
show all

LilyPond Beginnershandleiding

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

Delete template?

Save as template?