[fluid-dev] Re: fluid-dev Digest, Vol 13, Issue 4

[Stéphane Letz]

> The reason for this is that even though there is no problem for
> fluidsynth to become a client in Jack, there is no MIDI driver for
> fluidsynth (previously known as msSynthDriver) in the present version
> of MidiShare (1.87). So, fluidsynth cannot act as a MIDI source.
> (MidiShare did have this capability for iiwusynth.)
>
> According to my recent correspondence with Stéphane Letz, he and his
> colleagues are actively developing this driver under CVS.

Hum... not exactly...

They are two different things here:

- compiling fluidsynth as a standalone program that may use MidiShare 
for it's Midi input. You have compiled fluidsynth this way if I 
understand correctly. You should be able to get external Midi events 
with MidiShare and trigger fluidsynth in real-time.

- wrapping the flusidsynth  code  in a MidiShare driver so that 
fluidsynth can run as a MidiShare driver : a MidiShare driver is a 
dynamicall piece of code that will be loaded and activated by the 
MidiShare kernel when a MidiShare client is loaded.
 Having  flusidsynth as a MidiShare driver would allow then any 
MidiShare client (OpenMusic, Elody...) to access the fluidsynth driver.

The msSynthDriver code was this driver wrapper build around fluidsynth 
(actually iiwusynth). The CVS oce would need to be adapted to use the 
fluidsynth API instead of the iiwusynth API, but it shouid not be too 
complex.

Stephane