chiark / gitweb /
Merge branch 'arkkra' into shiny
[mup] / mup / docs / uguide / stuff.html
CommitLineData
69695f33
MW
1<HTML>
2<HEAD><TITLE>
3"Tempo, dynamic marks, ornaments, etc."
4</TITLE></HEAD>
5<BODY>
6<P>
7&nbsp;&nbsp;&nbsp;<A HREF="textstr.html">&lt;-- previous page</A>
8
9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="index.html">Table of Contents</A>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="textmark.html">next page --&gt;</A>
10</P>
11
12<H1>
13TEMPO, DYNAMIC MARKS, ORNAMENTS, ETC.
14</H1>
15<H2>
16General information
17</H2>
18<P>
19There are a number of symbols and other markings that appear frequently
20in music, which are normally associated with a particular time or place in the
21composition. There are several classes of such symbols, all of which are
22handled by Mup in a somewhat similar fashion. The general format of these
23statements is:
24<BR><PRE>
25<I>mark_type place staff(s) distance : begintime text duration;</I>
26</PRE><BR>
27</P>
28<P>
29The <I>mark_type</I> can be any of the following:
30<PRE>
31Mark_type Meaning
32
33rom text in roman font
34ital text in italic font
35bold text in bold font
36boldital text in bold-italic font
37mussym music symbol (fermata, coda sign, etc.)
38phrase phrase mark
39&lt; crescendo &quot;hairpin&quot;
40&gt; decrescendo &quot;hairpin&quot;
41octave play 1 or more octaves higher or lower
42pedal piano pedal marks
43</PRE>
44</P>
45<P>
46The <I>place</I> is as for
47<A HREF="lyrics.html">lyrics:</A>
48above, below, or between.
49There are some restrictions, as summarized below:
50<PRE>
51 place allowed
52mark_type above below between default
53
54rom yes yes yes above
55bold yes yes yes above
56ital yes yes yes above
57boldital yes yes yes above
58mussym yes yes yes above
59phrase yes yes no varies
60&lt; yes yes yes above
61&gt; yes yes yes above
62octave yes yes no none
63pedal no yes no below
64</PRE>
65</P>
66<P>
67<A HREF="octave.html">Octave marks</A>
68must include a <I>place</I> of above or below.
69For all the other mark_types, the <I>place</I> is optional. For
70<A HREF="phrase.html">phrase,</A>
71if <I>place</I> is not specified, Mup determines it
72on a case-by-case basis depending on the location of the notes.
73</P>
74<P>
75As with musical data or lyrics, the <I>staff</I> can be a single
76number or may include lists and ranges. In the case of &quot;between&quot;,
77staff numbers must be in pairs, separated by an &quot;&amp;&quot;, with the second
78staff number one greater than the first.
79</P>
80<P>
81The <I>staff</I> can also be specified by the keyword &quot;all,&quot; in which
82case the mark will be placed above the top visible staff or below the
83bottom visible staff.
84</P>
85<P>
86Here are some examples:
87<BR><PRE>
88rom 3:
89boldital below 1:
90&lt; between 3&amp;4:
91pedal below 2:
92octave above 3:
93phrase 3,4:
94mussym above 2-3, 5:
95ital between 1&amp;2, 3&amp;4:
96</PRE><BR>
97</P>
98<P>
99<A NAME="dist">The</A>
100<I>distance</I> is optional. It is specified by the keyword &quot;dist&quot; followed
101by a number. This number overrides the
102<A HREF="param.html#dist">dist,</A>
103<A HREF="param.html#chdist">chorddist,</A>
104or
105<A HREF="param.html#dyndist">dyndist</A>
106parameter value that would normally apply, and is given in stepsizes.
107If the number is followed by a ! the items will be placed at exactly that
108distance from the edge of the staff,
109without regard for anything they might overwrite.
110Otherwise the normal rules apply: the dist is a minimum value, and items
111may be placed farther away than this to avoid colliding with other things.
112If the ! is used, the number is allowed to be negative,
113which allows you to place items inside the staff.
114A dist cannot be specified with pedal, phrase, or between.
115<BR><PRE>
116score
117 dist=2
118music
119
120rom above 1: 1 &quot;normal dist&quot;;
121rom above 1 dist 4: 2 &quot;dist 4&quot;; // higher than usual
122rom above 1 dist 0! : 3 &quot;forced 0&quot;; // lower than normal
123mussym above 1 dist -2! : 4.5 &quot;rr&quot;; // forced down into staff
1241: c;;;;
125endbar
126</PRE><BR>
127<IMG SRC="mugex67.gif" ALT="Picture of Mup output"><BR>
128</P>
129<P>
130After the colon comes one or more items to be printed. Each item contains
131at least a begintime specification. Some may also contain a
132<A HREF="textstr.html">text string</A>
133and/or
134a duration. Each item ends with a semicolon. A newline ends the list of items.
135</P>
136<P>
137The begintime describes where in time the item should be printed. It is
138a number ranging from 0 to the numerator (top number)
139of the
140<A HREF="param.html#time">time signature</A>
141plus one.
1420 refers to the bar line at the beginning of the current measure, 1 refers
143to the first beat of the measure, 2 to the second beat, etc., with the
144maximum value referring to the bar line which ends the measure. A &quot;beat&quot;
145is whatever time value is given by the denominator (bottom number)
146of the time signature.
147For example, in 4/4 or 3/4 time, a beat is a quarter note, whereas in 6/8
148or 9/8 time, a beat is an eighth note. Fractional values can be specified
149using a decimal number. Thus 1.5 is halfway between beats 1 and 2,
150while 2.66 is about 2/3 of the way between beats 2 and 3.
151For
152<A HREF="param.html#time">time signatures</A>
153that are the addition of two or more fractions, like 4/4 + 3/8,
154a &quot;beat&quot; is given by the largest denominator.
155</P>
156<P>
157Since grace notes effectively take zero time, special notation is used
158to place something relative to a grace note. The <I>begintime</I> can be
159followed by a number of grace notes to &quot;back up&quot; from the beat.
160The number is a negative number enclosed in parentheses.
161</P>
162<P>
163The beat time value can optionally be followed by
164<A NAME="stepoff">an offset, in stepsizes.</A>
165This offset is a number in square brackets.
166The number must begin with a + or - sign.
167It can optionally include a decimal point and fractional part.
168A negative offset will cause the item to
169be moved to the left, while a positive offset will cause it
170to be moved to the right.
171This offset is used as a final adjustment after all the other placement
172has been done. A common use for this would be if you want to place something
173slightly before the beginning of the first measure of a song. You could
174then specify something like:
175<BR><PRE>
176rom above all: 0 [-3.5] &quot;Allegro&quot;;
177</PRE><BR>
178which would place the &quot;Allegro&quot; 3.5 stepsizes left of the beginning
179of the measure.
180</P>
181<P>
182The grace note back up, if any, must occur before the
183stepsize offset, if any.
184For example:
185<BR><PRE>
1861: c; [grace] 8d; []e; []f; 2.g;
187ital above 1: 2(-3)[+1] &quot;cresc.&quot;;
188bar
189</PRE><BR>
190<IMG SRC="mugex68.gif" ALT="Picture of Mup output"><BR>
191would find the chord at or closest to count 2,
192and back up 3 grace notes from there, then move right by 1 stepsize.
193</P>
194<P>
195For items that include a duration, the duration tells the ending point of
196the item. A duration is specified by:
197<BR><PRE>
198<B>til</B> <I>M</I><B>m</B> + <I>N</I>
199</PRE><BR>
200where <I>M</I> is a number of
201<A HREF="bars.html">bar lines</A>
202to cross, and <I>N</I> is a number of additional beats.
203If either of them is 0, it can be omitted,
204but at least one of them must be non-zero.
205Here are some examples:
206<BR><PRE>
207til 3 // until beat 3 of current measure
208til 1m+2 // until beat 2 of next measure
209til 1m // until next bar line
210</PRE><BR>
211</P>
212<P>
213Whether the text and duration are allowed or required depends on the mark_type,
214as summarized below:
215<PRE>
216mark_type text duration
217
218rom required optional
219bold required optional
220ital required optional
221boldital required optional
222mussym required allowed on tr only
223phrase not allowed required
224&lt; not allowed required
225&gt; not allowed required
226octave required optional
227pedal * or nothing not allowed
228</PRE>
229</P>
230<P>
231If there are several items, such that they have to be stacked on top
232of each other, all items of a particular class are placed from top to bottom
233according to input order. The classes are done in the order
234shown in the table below, unless the order is overridden by
235the
236<A HREF="param.html#aboveord">aboveorder,</A>
237<A HREF="param.html#beloword">beloworder,</A>
238or
239<A HREF="param.html#betwnord">betweenorder</A>
240parameters.
241<PRE>
242above (from bottom up)
243 phrase
244 mussym
245 octave
246 rom bold ital boldital &lt; &gt;
247 lyrics
248 endings
249 rehearsal marks
250
251below (from top down)
252 phrase
253 mussym
254 octave
255 rom bold ital boldital &lt; &gt;
256 lyrics
257 pedal
258
259between (from bottom up)
260 mussym
261 rom bold ital boldital &lt; &gt;
262 lyrics
263</PRE>
264</P>
265<P>
266For example, for the above items, all phrases will be placed as close to the
267staff as possible, then mussym items above them, then octave marks above
268them, etc. However, if there are several mussym items that belong at the
269same horizontal position, the first one entered in the input will be printed
270above the second, the second one entered will be printed above the third, etc.
271All of the &quot;above all&quot; items of a given class will be above the
272items of that class for the top visible staff,
273and all &quot;below all&quot; items of a given class will be below the
274items of that class for the bottom visible staff.
275<BR>
276<A HREF="textmark.html">Text</A>
277<BR>
278<A HREF="mussym.html">Music symbols</A>
279<BR>
280<A HREF="phrase.html">Phrase marks</A>
281<BR>
282<A HREF="cres.html">Crescendo and decrescendo marks</A>
283<BR>
284<A HREF="octave.html">Octave marks</A>
285<BR>
286<A HREF="pedal.html">Piano pedal marks</A>
287<BR>
288<A HREF="roll.html">Rolls</A>
289</P>
290<HR><P>
291&nbsp;&nbsp;&nbsp;<A HREF="textstr.html">&lt;-- previous page</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="index.html">Table of Contents</A>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="textmark.html">next page --&gt;</A>
292</P>
293</BODY></HTML>