1 Apr
2006
1 Apr
'06
3:27 p.m.
Paul Davis wrote:
On Sat, 2006-04-01 at 13:33 +0300, Sampo Savolainen
wrote:
Thanks Paul. This is what I was hoping to hear. At RFA they probably
don't want Rivendell's caed (core audio engine daemon) getting kicked
out by jack in the middle of a broadcast.
-Eric Rz.
On Sat, 2006-04-01 at 03:02 -0500, Eric Dantan
Rzewnicki wrote:
In practice yes. There is no point in running both in softmode
and
realtime. The worst case scenario is that a client gets deadlocked
within the process() thread and takes over jackd (in the absolutely
worst case, the whole computer) as the jack watchdog thread doesn't kill
the client.
actually, this is the opposite of the intent.
softmode is there mostly for people who want to use JACK in, for
example, live situations where the occasional xrun is not a disaster.
they want realtime latency settings, but don't want any clients kicked
out if there is an xrun. if the watchdog doesn't work in softmode, its a
bug. -s,
--softmode
Ignore xruns reported by the ALSA driver. This makes JACK less
likely to disconnect unresponsive ports when running without
--realtime.
So, to be clear, this means that softmode and realtime are
effectively
mutually exclusive?