
 RecordAPI
 =========

 This is a demonstration of how to write a sample driver for ProSound.

 Files
 -----
 The following files/directories are include in the RecordAPI directory:
 
 !RunDISABLED  If you want to try the sample driver then rename this to
               !Run; the !Run file is run by ProSound when it starts; !Run
               simply checks if the application !RecordAPI is running and
               starts it if not.
             
 FX            ProSound requires the FX file - in this case it is a BASIC
               library; ProSound requires that the library provides an FN
               with the same name as the directory.

 !RecordAPI    The actual sample driver application.
 
 ReadMe        This file.

 Principles
 ----------
 ProSound communicates with the sample drivers by using Wimp messages.
 The sample driver sends messages to ProSound about the availability of
 drivers, and ProSound sends messages to the sample driver about the
 location in shared memory of a block of memory to be used for buffers.
 
 The sample driver fill the buffer with the recorded samples, and ProSound
 reads the content of the buffer and writes samples to disc.
 
 In real life the sample driver would probably communicate with some kind
 of interrupt driver module with talks to the hardware. ProSound expects
 recording to be done multitasking.

 Details
 -------
 The layout of the shared memory is described at the end of the file
 !ProSound.ProLib, the variables RecAPI_XXX% (where XXX is a name in
 uppercase) hold the offsets of various information.

 The content of each Wimp message is describe in !RecordAPI.!RunImage.

 Copyright
 ---------
 (C) Henrik Bjerregaard Pedersen, 2016
 
 The entire content of the RecordAPI directory is released under the GPL
 (any version).


 Henrik Bjerregaard Pedersen
 henrikbp@vip.cybercity.d
