Dave Phillips skrev:
<...>
Zyn will occasionally just pop itself out of the JACK graph, I'm not
sure why.
I understand where this is coming from and Zyn is at fault here but the
problem is not as grave as one can be led to believe, Zyn does not HAVE
to be popped out.
This all stems from the fact that Jack by default kicks all clients that
cannot, for whatever reason, meet the deadline for each roundtrip.
Personally I don't think this is a good practice outside of a
development environment, the data may still be useful and the incident
will be logged.
It's a bit like using asserts to make sure you're catching ugly problems
during development but in the release-version asserts are normally disabled.
It is very easy to reconfigure jack to give all applications some slack
using:
jackd -t 4000 -d <backend> -s <your favourite parameters>
-t 4000 extends timeout to 4000 milliseconds
-s sets jack in softmode (set for the backend I believe)
(I think that's the right parameters, don't have acccess to a system
right now.)
Regards,
Robert
