Commit | Line | Data |
---|---|---|
69695f33 MW |
1 | <HTML> |
2 | <HEAD><TITLE> | |
3 | Octave marks | |
4 | </TITLE></HEAD> | |
5 | <BODY> | |
6 | <P> | |
7 | <A HREF="cres.html"><-- previous page</A> | |
8 | ||
9 | <A HREF="index.html">Table of Contents</A> <A HREF="pedal.html">next page --></A> | |
10 | </P> | |
11 | ||
12 | <H2> | |
13 | Octave marks | |
14 | </H2> | |
15 | <P> | |
16 | Octave statements are used to mark notes that are to be played one or more | |
17 | octaves higher or lower than written. An "octave above" statement is | |
18 | used to specify playing higher than written, or "octave below" for playing | |
19 | lower than written. Each item must include a begintime | |
20 | and a text string. The text string is most typically "8va". | |
21 | It will always be printed in 12-point times italics font. If the octave | |
22 | shifting applies to more than a single chord, there should also be a | |
23 | duration specified, reaching to include the last affected note. In this | |
24 | case, Mup will draw a dashed line to mark the span affected. Note that | |
25 | specifying the exact beat of a chord indicates the horizontal center of the | |
26 | chord, so if you want the dashed line to reach a bit past the note, it | |
27 | will be necessary to specify a duration slightly beyond the point of | |
28 | the last chord to be included. Examples: | |
29 | <BR><PRE> | |
30 | 1: 2f;g; | |
31 | 2: 2d+;g; | |
32 | 3: 2g;ce; | |
33 | octave above 1: 2 "8va" til 1m + 1.3; | |
34 | bar | |
35 | 1: 2a;c; | |
36 | 2: 2f;e; | |
37 | 3: 4f;;c;; | |
38 | octave below 2: 1 "8va"; | |
39 | octave below 3: 1 "8va" til 2.5; 3 "15" til 4.5; | |
40 | bar | |
41 | </PRE><BR> | |
42 | <IMG SRC="mugex76.gif" ALT="Picture of Mup output"><BR> | |
43 | </P> | |
44 | <HR><P> | |
45 | <A HREF="cres.html"><-- previous page</A> <A HREF="index.html">Table of Contents</A> <A HREF="pedal.html">next page --></A> | |
46 | </P> | |
47 | </BODY></HTML> |