Bug#527642: jackd: jack daemon quits at boot up

[Adrian Knoth]

On Sat, May 09, 2009 at 12:35:46PM +0100, Philip Ashmore wrote:

> So, long story short (too late) removing -R and -P seems to fix this, but

OK.

> 1. Dropouts seem to depend on the -p (max ports) setting, something it 
> definitely should not do.

You're mistaken here. -p is the buffer size, and increasing the buffers
makes the system more reliable, hence less dropouts. Perfectly as
expected.

(and without -R, you're very likely getting xruns/dropouts)

> 2. No system logging in jackd isn't helping.

That's mostly because jackd is not supposed to be a system daemon.

> 3. Qjackctl can't seem to determine what the settings of an already
> started jackd daemon are. I noticed that when I quit qjackctl it
> caused a dropout once.

Out of scope. This bug isn't about qjackctl and its features.


One last comment, but a pretty important one: jackd is not supposed to be a
system sound server. It's intended for professional audio production, and
running it to output KDE sounds or whatsoever is discouraged by upstream.
That's why you usually start it as a user, let ardour start it or something
similiar, but not at system startup.

Usually, all the apps run within locked memory, so no page faults or
swapping would ever interrupt the audio stream. (that's what -R does and
that's why you need to increase memlock).

Running generic sound apps in this locked realtime context is error-prone, at
least it's not the intended use case.

Since Fedora doesn't come with an init script for jackd, I'm
contemplating to remove it from Debian, too.


Cheerio

-- 
mail: adi at thur.de  	http://adi.thur.de	PGP/GPG: key via keyserver