LilyPond Beginnershandleiding

More documents

Recommendations

Info

Hoofdstuk 4: Tweaking output 116 c2^"Text3" c2^"Text4" | Text1 Text2 Text3 Text4 The command to revert to the default behavior is \textLengthOff. Remember \once only works with \override, \set, \revert or \unset, so cannot be used with \textLengthOn. Markup text will also avoid notes which project above the staff. If this is not desired, the automatic displacement upwards may be turned off by setting the priority to #f. Here’s an example to show how markup text interacts with such notes. % This markup is short enough to fit without collision c2^"Tex" c'' | R1 | % This is too long to fit, so it is displaced upwards c,,2^"Text" c'' | R1 | % Turn off collision avoidance \once \override TextScript.outside-staff-priority = ##f c,,2^"Long Text " c'' | R1 | % Turn off collision avoidance \once \override TextScript.outside-staff-priority = ##f \textLengthOn % and turn on textLengthOn c,,2^"Long Text " % Spaces at end are honored c''2 | Tex Dynamics placement Text Long Text Long Text Dynamic markings will normally be positioned beneath the staff, but may be positioned above with the \dynamicUp command. They will be positioned vertically relative to the note to which they are attached, and will float below (or above) all within-staff objects such as phrasing slurs and bar numbers. This can give quite acceptable results, as this example shows: \clef "bass" \key aes \major \time 9/8 \dynamicUp bes4.~\f\< \( bes4 bes8 des4\ff\> c16 bes\! | ees,2.~\)\mf ees4 r8 |
Hoofdstuk 4: Tweaking output 117 8 9 f ff mf However, if the notes and attached dynamics are close together the automatic placement will avoid collisions by displacing later dynamic markings further away, but this may not be the optimum placement, as this rather artificial example shows: \dynamicUp a4\f b\mf c\mp b\p mp p f mf Should a similar situation arise in ‘real’ music, it may be preferable to space out the notes a little further, so the dynamic markings can all fit at the same vertical distance from the staff. We were able to do this for markup text by using the \textLengthOn command, but there is no equivalent command for dynamic marks. So we shall have to work out how to do this using \override commands. Grob sizing First we must learn how grobs are sized. All grobs have a reference point defined within them which is used to position them relative to their parent object. This point in the grob is then positioned at a horizontal distance, X-offset, and at a vertical distance, Y-offset, from its parent. The horizontal extent of the object is given by a pair of numbers, X-extent, which say where the left and right edges are relative to the reference point. The vertical extent is similarly defined by a pair of numbers, Y-extent. These are properties of all grobs which support the grob-interface. By default, outside-staff objects are given a width of zero so that they may overlap in the horizontal direction. This is done by the trick of adding infinity to the leftmost extent and minus infinity to the rightmost extent by setting the extra-spacing-width to '(+inf.0 . -inf.0). So to ensure they do not overlap in the horizontal direction we must override this value of extra-spacing-width to '(0 . 0) so the true width shines through. This is the command to do this for dynamic text: \override DynamicText.extra-spacing-width = #'(0 . 0) Let’s see if this works in our previous example: \dynamicUp \override DynamicText.extra-spacing-width = #'(0 . 0) a4\f b\mf c\mp b\p | mp f mf p Well, it has certainly stopped the dynamic marks being displaced, but two problems remain. The marks should be spaced a little further apart and it would be better if they were all the same distance from the staff. We can solve the first problem easily. Instead of making the extra-spacing-width zero we could add a little more to it. The units are the space between two staff lines, so moving the left edge half a unit to the left and the right edge half a unit to the right should do it:
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:
Page 69 and 70: 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 and 118: Hoofdstuk 4: Tweaking output 113 5
Page 119: Hoofdstuk 4: Tweaking output 115 Sl
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 143 and 144: Hoofdstuk 4: Tweaking output 139
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?