Commit | Line | Data |
---|---|---|
69695f33 MW |
1 | <HTML> |
2 | <HEAD><TITLE> | |
3 | Mup debugging | |
4 | </TITLE></HEAD> | |
5 | <BODY> | |
6 | <P> | |
7 | <A HREF="param.html"><-- previous page</A> | |
8 | ||
9 | <A HREF="index.html">Table of Contents</A> <A HREF="adjust.html">next page --></A> | |
10 | </P> | |
11 | ||
12 | <H2> | |
13 | Debugging | |
14 | </H2> | |
15 | <P> | |
16 | Since Mup requires its input in a fairly strict format, when a song is put | |
17 | in, it may contain "typos." Generally, the error messages that Mup prints | |
18 | will give you an idea of what is wrong. However, sometimes Mup is not able | |
19 | to recognize that something is wrong until some distance beyond the actual | |
20 | error. If you can't find anything wrong with the line that Mup lists as | |
21 | being in error, try looking at the end of the previous line, or even earlier | |
22 | lines. Some of the most common problems are missing semicolons and missing | |
23 | quotes. Missing quote marks tend to be especially confusing to Mup, and may | |
24 | cause many error messages, even though there is only one problem. | |
25 | Another common problem that may cause a very large number of error messages is | |
26 | forgetting to state "music" to enter music context. | |
27 | </P> | |
28 | <P> | |
29 | Often listening to | |
30 | <A HREF="midi.html">MIDI output</A> | |
31 | is much more effective at spotting things like wrong notes and missing | |
32 | accidentals than trying to find them by eye. | |
33 | </P> | |
34 | <HR><P> | |
35 | <A HREF="param.html"><-- previous page</A> <A HREF="index.html">Table of Contents</A> <A HREF="adjust.html">next page --></A> | |
36 | </P> | |
37 | </BODY></HTML> |