Re: [fluid-dev] New CoreMIDI driver for Mac OSX

[Ebrahim Mayat]

On Jan 10, 2009, at 2:46 PM, Pedro Lopez-Cabanillas wrote:

> A test case: If you have MidiShare installed, both drivers will be  
> compiled.
> MidiShare takes priority by default at runtime in this case.
Right, just invoking "fluidsynth -a jack" starts fluidsynth with  
MidiShare as the default MIDI driver.

For using CoreMIDI one needs to do something like "fluidsynth -m  
coremidi".

On the other hand, qsynth works equally well with both drivers....if  
one chooses "coremidi" then quit qsynth then re-launch qsynth, qsynth  
starts with coremidi as the MIDI driver. So as you might expect qsynth  
memorizes its settings on quitting.

> Another possible issue: only one virtual port is created. The other  
> synth I've
> tested (SimpleSynth - www.apple.com/downloads/macosx/audio/simplesynth.html)
> has the option of connecting to an existing bus, in addition. I  
> don't know if
> this option is really necessary.

I don't think that is necessary.

Using a simple MIDI interface with two ins and two ouputs, I was able  
two trigger fluidsynth with one and linuxsampler or SimpleSynth with  
the other. Bearing in mind that since all the major software  
commercial sequencers and soft synths like Logic, Cubase, Live,  
Atmospherics etc. are bundled with CoreMIDI support, one can, using a  
multiport external hardware MIDI patchbay, create a complex setup.

Greetings,
E