[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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
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
Thomas Meyssonnier, thank you for reporting this and helping make Ubuntu
better. Could you please test the latest upstream kernel available from
the very top line at the top of the page (the release names are
irrelevant for testing, and please do not test the daily folder)
following
** 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.
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
** Tags added: amd64 apport-bug latest-bios-1.21 trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1402196
Title:
Behringer UMC404 USB2 audio interface disconnects when initialized
Thomas Meyssonnier, given that it went from not working at all, to it's
working in a non-preferred way, it would seem helpful to identify this
commit (and in turn the committer) in order to advise them on how it's
improved but may need more work by them. Hence, the next step is to
fully reverse
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
9 matches
Mail list logo
