Commit | Line | Data |
---|---|---|
69695f33 MW |
1 | <HTML> |
2 | <HEAD><TITLE> | |
3 | Manually placed tuplet numbers | |
4 | </TITLE></HEAD> | |
5 | <BODY> | |
6 | <P> | |
7 | <A HREF="sharehd.html"><-- previous page</A> | |
8 | ||
9 | <A HREF="index.html">Table of Contents</A> <A HREF="manual.html">next page --></A> | |
10 | </P> | |
11 | ||
12 | <H2> | |
13 | Manually placed tuplet numbers | |
14 | </H2> | |
15 | <P> | |
16 | Generally, Mup will place | |
17 | <A HREF="tuplets.html">tuplet</A> | |
18 | numbers for you. | |
19 | However, you do need to print them yourself on | |
20 | <A HREF="ichdattr.html#crossbm">cross-staff beams.</A> | |
21 | And there may be cases where you choose | |
22 | to use 'n' to turn off Mup's automatic printing of tuplet numbers, | |
23 | in order to print them manually in a different place than Mup would. | |
24 | Mup normally uses newcentury boldital font for tuplet numbers, in 11-point | |
25 | size for regular notes and 9-point for cue notes. | |
26 | So to make your manually placed tuplet numbers | |
27 | look the same as automatic ones, you might use a | |
28 | <A HREF="macros.html">macro</A> | |
29 | something like this: | |
30 | <BR><PRE> | |
31 | define TUPNUM(NUM) "\f(NX)\s(11)" +`NUM` @ | |
32 | 1: { 8c; d; e; } 3n; 2.us; | |
33 | rom above 1 dist0: 1.34 TUPNUM(3); | |
34 | bar | |
35 | </PRE><BR> | |
36 | Or another approach would be something like this: | |
37 | <BR><PRE> | |
38 | define TN(NUM,WHERE,D,N) newcentury boldital WHERE dist D: N `NUM`;@ | |
39 | 1: { 8c; d; e; } 3n; 2.us; | |
40 | TN(3,above 1,0,1.34) | |
41 | bar | |
42 | </PRE><BR> | |
43 | </P> | |
44 | <HR><P> | |
45 | <A HREF="sharehd.html"><-- previous page</A> <A HREF="index.html">Table of Contents</A> <A HREF="manual.html">next page --></A> | |
46 | </P> | |
47 | </BODY></HTML> |