Sophie

Sophie

distrib > Fedora > 18 > x86_64 > by-pkgid > c67286ade4f05f2be65d530517d37cab > files > 42

mup-6.2-1.fc18.x86_64.rpm

<HTML>
<HEAD><TITLE>
Mup debugging
</TITLE></HEAD>
<BODY>
<P>
&nbsp;&nbsp;&nbsp;<A HREF="param.html">&lt;-- previous page</A>

&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="index.html">Table of Contents</A>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="mupindex.html">Index</A>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="adjust.html">next page --&gt;</A>
</P>
           
<H2>
Debugging
</H2>
<P>

Since Mup requires its input in a fairly strict format, when a song is put
in, it may contain &quot;typos.&quot; Generally, the error messages that Mup prints

will give you an idea of what is wrong. However, sometimes Mup is not able
to recognize that something is wrong until some distance beyond the actual
error. If you can't find anything wrong with the line that Mup lists as
being in error, try looking at the end of the previous line, or even earlier
lines. Some of the most common problems are missing semicolons and missing

quotes. Missing quote marks tend to be especially confusing to Mup, and may
cause many error messages, even though there is only one problem.
Another common problem that may cause a very large number of error messages is
forgetting to state &quot;music&quot; to enter music context.


</P>
<P>
Often listening to
<A HREF="midi.html">MIDI output</A>
is much more effective at spotting things like wrong notes and missing
accidentals than trying to find them by eye.
</P>
<HR><P>
&nbsp;&nbsp;&nbsp;<A HREF="param.html">&lt;-- previous page</A>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="index.html">Table of Contents</A>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="mupindex.html">Index</A>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="adjust.html">next page --&gt;</A>
</P>
</BODY></HTML>