[freesci-develop] cvs: cvsuser

[freesci-develop]

CVSROOT:        /home/cvs
Module name:    freesci
Changes by:     cvsuser 01/02/28 13:14:04

Modified files:
        src/include    : Makefile.am sound.h 
        src/sound      : Makefile.am soundserver_null.c 
Added files:
        src/include    : midi_mt32.h midiout.h 
        src/sound      : midi_mt32.c midiout.c 

Log message:
Okay, I'm ramping up to getting some working midi output.  *teehee*
(took me long enough...)

(D'oh; I forgot to include the ChangeLog.  Owel; I'll add it in my next
commit latter today)

Okay:  Headers cleaned up.
'null' midiout driver that just reports what it gets sent.
the mt32 midi code out of /sfx

Next up:

1)      Soundserver_null sends midi events on everything.
2)      Automagically send over patch.001 ***
3)      Add in real midiout drivers.  But first finish the
output api and define it properly (like the gfx driver)

***  Now I'm trying to figure out the best way to do this -- how does
real SCI handle this?  I know the sound server tells the game what
patch to use, but how is this actually handled?  Through what
command(s)?   Needless to say, we won't get anthing useful out of
the mt32 unless we dump the patch over..

- Pizza