[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] Multiple jack clients == really bad

From: David Henningsson
Subject: Re: [fluid-dev] Multiple jack clients == really bad
Date: Sat, 17 Oct 2009 13:26:25 +0200
User-agent: Thunderbird (X11/20090817)

address@hidden wrote:
While doing some testing of the MIDI parser, using the Jack MIDI driver, I discovered that FluidSynth would semi-randomly lose connection with Jack on startup.

Seems bad. I guess most people with Jack use the ALSA MIDI drivers, right?

It seems Jack (at least 116.1) doesn't like to have multiple client connections. Currently the Jack audio driver and Jack MIDI driver create separate client connections. In addition, I discovered that PortAudio will also create a Jack client connection when you initialize the library. In order to have the list of PortAudio devices in the audio.portaudio.device, PortAudio is initialized even if it doesn't get used. We may be able to get around this by de-initializing the driver at the end of getting the device list.

If it is causing trouble for more people than it solves problems for; we could consider disabling the PortAudio driver by default (i e people have to provide a configure switch to enable PortAudio).

At any rate, some work cut out for me, to merge the JACK audio and MIDI drivers. I already kind of hacked it somewhat, but its a bit too messy for my taste.

Yet another status report, as we count down to the release of 1.1.0. Any reports on testing would be greatly appreciated. I'm trying to test as much as I can, but its hard to cover every usage scenario.

From what I've tested it looks fine. Either that, or I try to fix it ;-)

// David

reply via email to

[Prev in Thread] Current Thread [Next in Thread]