Re: [fluid-dev] Jack and CoreAudio are mutually exclusive

[Ebrahim Mayat]

On Tue, 2009-11-17 at 16:57 -0800, address@hidden wrote:
> Hello Ebrahim,
//
> 
> It sounds as if you may have multiple audio interfaces?  I notice that  
> the FluidSynth coreaudio driver doesn't currently have support for  
> specifying which audio device to use.  Seems a call to  
> AudioDeviceGetProperty() is failing when attempting to get the default  
> buffer size.  I'm not sure why that would happen though, but perhaps  
> its using the wrong audio device?  The driver could be improved to  
> display what the particular failure is which would help diagnose the  
> problem.
> 
Hello Josh

Well, I do not own a Firewire device yet but since the use of these
devices is now coming into the mainstream on both Linux and OS X, I
thought this is one point you might consider as a possible feature
addition in the near future.

I tried running fluidsynth with different -z values and this does not
have any effect. So yeah, AudioDeviceGetProperty() could be one area
that could be refactored.

The other point is that (if you excuse the pun) Jack seems to hijack
CoreAudio. If JackOSX remains installed and I run `fluidsynth -a
coreaudio...' the jackd server daemon is started and audio is rendered.
So, the "incompatibility" problem could lie with JackOSX ?

E

P.S. The doxygen-based documentation is highly-detailed and a welcome
addition. Many thanks to all who worked on it.