File: midiplay.txt
SGoldthorpe	20-Jul-91

This software is (C) 1991 Stephen Goldthorpe but it's FREE!  Usual
disclaimers and notices about this software not being sold for profit.
But you may take all you want from the code though!  If you have any
suggestions/bug fixes please get in contact with me.  I don't want to
maintain code i've never even seen before (life's hard enough without all
of that)!
					-Steve Goldthorpe
Phone (DAYTIME UK):	+44 707 382350
Internet E-Mail:	SGoldthorpe.wgc-e@rx.xerox.com
			goldthor@arisia.xerox.com

midiplay 0.5
============

 *
 * Version 0.5 by Piet van Oostrum <piet@cs.ruu.nl>
 * November 1991.
 * I made the following changes:
 * 1. Files > 32767 wouldn't play. I have changed a couple of ints to
 *    LONG. Also malloc'ed the buffer with a variable rather than a fixed size.
 * 2. replaced array referenced with a[i] rather than *(a+i). I find this
 *    more readable but it has the same meaning.
 * 3. Midifiles of more than about 3 minutes didn't play right. I think
 *    this is a bug in ltod (long to double) in the floating point lib. I
 *    changed the timing from using floating point arithmetic to LONG
 *    arithmetic.
 *    Anyway the timing was not robust in the presence of tempo changes
 *    because the new time per beat would be applied to the time from the
 *    beginning of the piece rather than from the time of the tempo change.
 * 4. I introduced the -T option to send timing commands. This can be
 *    used to trigger a drum computer or an arranger.
 *
 * NOTE: I distribute this version with the consent of Steve
 * Goldthorpe. I think he should not be bothered with bugs in my version!

midiplay 0.4
============

To see what's new in this version of midiplay use the -h flag.

midiplay is designed to be run in a command line environment (I use gulam)
and so if run from GEM text may disappear before you have a chance to read
it.  If you don't use a CLI see gem_mp below otherwise ignore it.

example usage:
	midiplay	-i d:\polonase

gem_mp
======
This program simply calls midiplay with the arguments passed to it.  It clears
the screen before calling midiplay and waits for you to press RETURN before
exiting, so the information on the screen won't go away before you are ready.
gem_mp must be in the same folder as midiplay as this is how it finds midiplay.

example usage:
	click on gem_mp from gem and type in the parameter box:-
			-i d:\polonase

Many thanks to the sozobon & dblibs gang and to all those unhealthy things that
keep one going!
						-Steve Goldthorpe Jul 91