[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [fluid-dev] Re: fluid-dev Digest, Vol 13, Issue 4
From: |
Ebrahim Mayat |
Subject: |
Re: [fluid-dev] Re: fluid-dev Digest, Vol 13, Issue 4 |
Date: |
Tue, 16 Mar 2004 21:35:52 +0200 |
On Mar 16, 2004, at 9:00 PM, Stéphane Letz wrote:
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.
Hi Stéphane
Yes, I can trigger MIDI events in msDisplay from my external MIDI
keyboard but fluidsynth is not recognized by MidiShare when I try to
set up connections between my MIDI interface and fluidsynth in
msDrivers. So when I play my external MIDI keyboard with MidShare and
fluidsynth running, nothing happens. How would I be able to trigger
fluidsynth in real-time from the MIDI controller keyboard?
- 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.
This is something that I would also like to be developed. I am keeping
my eyes peeled.
Best Regards.
Ebrahim