X-Git-Url: https://git.distorted.org.uk/~mdw/mup/blobdiff_plain/cdb3c0882392596f814cf939cbfbd38adc6f2bfe..ddf6330b56bcfb657e0186b24b9b1422c51d3424:/mup/docs/uguide/debug.html diff --git a/mup/docs/uguide/debug.html b/mup/docs/uguide/debug.html new file mode 100644 index 0000000..bf675b8 --- /dev/null +++ b/mup/docs/uguide/debug.html @@ -0,0 +1,37 @@ + + +Mup debugging + + +

+   <-- previous page + +     Table of Contents    next page --> +

+ +

+Debugging +

+

+Since Mup requires its input in a fairly strict format, when a song is put +in, it may contain "typos." 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 "music" to enter music context. +

+

+Often listening to +MIDI output +is much more effective at spotting things like wrong notes and missing +accidentals than trying to find them by eye. +

+

+   <-- previous page     Table of Contents    next page --> +

+