
These library files are presented as a proof-of-concept.
They need much more work to make them "musical". An awful lot of them
were developed by recording the auto-accomp on my Casio keyboard and
then re-creating.

Some initial guidelines.... (changed from Beta 0.1)

>> Start each file with the BEGIN DOC/END section. In this header
	we are putting the following doc fields:
	
	Note     a descriptive comment, used in the library reference header
	File     the filename (not used)
	Author   Bob's name (not used)


>> Add a DocDefine to the end of each goove definition. You could do
	something like:
	
		Doc Defines Waltz This is a nice waltz groove.
		
	But, it is much easier to do it like this:
	
		DefGroove Waltz This is a nice waltz groove.
		
	Not only do we eliminate a time wasting near-duplicate line,
	but we ensure that the comment goes with the proper DefGroove.
	I think there is a better chance of getting the comment right this
	way, instead of sticking a bunch of 'Defines' in the top block.

	
>> Be as descriptive as possible in the pattern and groove names.
	Probably not as easy as it sounds ... but punct. and digits
	are permitted in pattern/groove names. Just remember that
	they are case-insensitive.

	Also, let's use lots of comments and blank lines.
		
>> Try not to overwrite common names. There are no warnings for this,
	and it could create unwanted results. With auto-loading of groove
	name duplicates become more problematical!
	
>> Including voice, volume, random settings in a groove is probably
	a good idea. Easy enough for a user to override after he/she
	selects.

>> Everyone assumes that you are using a TIME setting of 4. If you want to
	define a Waltz, 6/8, 5/4 or whatever comment the file and use
	the time setting in the groove. See 'waltz' for examples.
		
>> It is probably a bad idea for library files to include other library files.



