Okay, I found the bug goes less severe as soon as kernel 3.13.2, which is to
say I bisected kernels from 3.18.0 down only to find this was mostly fixed a
long time since. The bug for duplex is more severe in older versions, causing
jackd to crash in 3.13.2 while 3.18.0 only has continuous xruns.
Kernel 3.18 fixes the bug only for playback-only or capture-only mode,
with rates up to 96kHz (the maximum) and latency down to 2ms. Duplex
modes still have a great number of xruns (every 5-10s), even with very
conservative settings (44.1kHz, 1024 frames/period, 3 periods/buffer),
and mostly the sa
** Tags removed: amd64 apport-bug latest-bios-1.21 trusty
** Tags added: kernel-bug-exists-upstream-3.18
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Also, in the above test case the interface has to be unplugged and re-
plugged when jackd is stopped and restarted, otherwise another error
occurs.
I also tried with another (USB1.1) interface and there is no such
problem.
--
You received this bug notification because you are a member of Kernel
Further testing reveals the interface works with playback only at 44.1kHz, 1024
frames, 3 periods.
However there are continual clicks when playing audio, while jackd does not
report xruns.
Jackd does start at 48 or 96 kHz, or with 128 frames/period, but then there is
no sound (but no errors eith
Public bug reported:
My audio interface, a Behriger UMC404, disappears from both lsusb and
/proc/asound/cards as soon as I start jackd (JACK 2). This results in
jackd failing because the card is missing. It reports a "protocol error"
which I think refers to the USB link. See attached syslog messag
6 matches
Mail list logo
