		~~~~~~~~~~~~~
		 GLOCKENCORD
		~~~~~~~~~~~~~
	        version 1.1.2
		~~~~~~~~~~~~~
		Error message
		 information
		~~~~~~~~~~~~~
Please note: versions 1.1.1 and 1.1.2 are functionally identical to version
1.1, and version 1.1 GCR files are still used.

Overview
--------
This file lists the error messages that can be produced by Glockencord
with more information for each than is provided on the screen of the DS
when the error occurs. They are listed in alphabetical order (of the
text displayed on-screen).

A lot of the error messages relate to file handling during use of
Automatic mode. Information to help avoid these errors is provided in
the instructions provided to create Glockencord music rolls.

In cases where the error relates to the formatting or content of a
musicroll ("gcr") file, it is possible that there is a bug in the GCR
compiler if that has been used to generate the music roll: In such cases
I'd like to be told so I can check it: My email address is at the bottom
of the read-me file.

CANNOT OPEN THE ROLL

There is no GCR file in the /DATA/glockencord folder which relates to the
name provided in the musicrolls.ini file.

DESCRIPTION TOO LONG IN MUSICROLLS.INI FILE

The description which accompanies the name of the file should not exceed
26 characters in length.

EMPTY MUSIC ROLL

There is no first line in the GCR file. This line should consist of "GCR"
(without the quotes) followed by a comma and then the version/variant
number of the music roll. Refer to the file "Creating rolls" for
further information.

FILENAME TOO LONG IN MUSICROLLS.INI FILE

The filename of the musicroll (GCR file) as provided in the musicrolls.ini
file exceeds 11 characters. Choose a shorter filename.

INVALID MUSIC ROLL

The first field of the first line should be "GCR" (without the quotes).
Refer to the file "Creating rolls" for further information.

INVALID ROLL UNKNOWN BYTE xx HEX NOTE: x BYTE: x

All the bytes defining notes in the Music roll (GCR file) must have the
top bit set to 0 and the following bit set to 1. The hex code of the
offending byte is provided by "xx" in the message. The Note and byte
values provided indicate the location of the faulty byte. Refer to the
file "Creating rolls" for further information.

LINE x OF THE MUSICROLLS.INI FILE CONTAINS NO INFORMATION

The line of the musicrolls.ini file specified by the given linenumber
("x") is empty.

LINE x TOO LONG IN MUSICROLLS.INI FILE

Lines in the /DATA/glockencord/musicrolls.ini file must not exceed 39
characters.

MISSING LINE 2

The Music roll loaded does not have a second line. This line should define
the number of voices in the roll and the tempo. Refer to the file "Creating
rolls" for further information.

MISSING LINE 3

The Music roll loaded does not have a third line. This line should contain
flags indicating whether voices are percussive. Refer to the file "Creating
rolls" for further information.

MUSIC TOO FAST

The tempo defined for the music roll is too high: It needs to be below
20 beats per second.

MUSIC TOO SLOW

The tempo defined for the music roll is too low: It needs to be at least
half a beat per second.

NO END MARKER

The music roll file should be terminated with the word END (on it's own line).

NOT VERSION 1.1

Glockencord version 1.1 expects the version number of the musicroll (GCR
file) to be 1.1. Refer to the file "Creating rolls" for further
information.

THE FILE MUSICROLLS.INI IS EMPTY

Although the file /DATA/glockencord/musicrolls.ini exists, it is empty.
Refer to the file "Creating rolls" for further information.

THE MUSICROLL COUNT IN MUSICROLLS.INI DOES NOT TALLY WITH THE NUMBER DEFINED

The number in the first line of the musicrolls.ini file is higher than
the number of lines which follow it.

THERE ARE NO MUSIC ROLLS

The first line of the file musicrolls.ini does not specify a number of
music rolls: This should be a simple count of the number of lines in
the musicroll.ini file after the first line.

UNABLE TO FIND MUSICROLLS.INI IN THE DATA FOLDER

The file "/DATA/glockencord/musicrolls.ini" could not be found (or could not
be opened). Ensure that the file is located and spelt in exactly the way shown
in this explanation, ignoring the quotes (eg: all lowercase).
