Due to a JACK bug that introduces a 5 second stall (JACK bug #248), my Darkice
instance dies rather often. This is because the JACK module has a short timeout
in its canRead function. This might be appropriate sometimes, but as I'm using
it to drive an internet radio station I'd rather it was more patient. I'd
suggest a default generous timeout (say 30 seconds? After a 30 second stall it
seems a good bet it's not coming back) plus perhaps a configuration value so
that users who really want it to die on a short period of unresponsiveness can
have it do so.
For perspective, the default JACK timeout for a badly behaved application is
500msec, so all it takes to kill Darkice is two badly behaved apps in its graph
or a generous -t setting starting JACK.
Original issue reported on code.google.com by chris.sm...@gmail.com on 27 Dec 2011 at 10:06
Original issue reported on code.google.com by
chris.sm...@gmail.com
on 27 Dec 2011 at 10:06