Hi,
this was a problem in jack itself and has been fixed somewhere between
version 0.109.2 and 0.116.1. Please update :)
Best
Benjamin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
I've the same behaviour on my Lenny system:
alsa_pcm: xrun of at least 1226435427565.568 msecs
Here some more information:
ii jackd0.109.2-3
ii linux-image-2.6.25-2-686 2.6.25-7
ii linux-image-2.6.26-1-686 2.6.26-8
It seems to be a
Yes, I no longer get these xrun messages now.
- Torquil
On Thursday 17 July 2008 00:33:17 Eric Dantan Rzewnicki wrote:
> Is your issue solved by the recommendation to use 3 periods that you got
> from the jack list?
>
> On Wed, Jul 16, 2008 at 09:06:04PM +0200, Torquil Macdonald Sørensen wrote:
>
Is your issue solved by the recommendation to use 3 periods that you got
from the jack list?
On Wed, Jul 16, 2008 at 09:06:04PM +0200, Torquil Macdonald Sørensen wrote:
> Package: jackd
> Version: 0.109.2-3
> Severity: normal
>
> After starting jackd with realtime priority, as a non-root user (us
Package: jackd
Version: 0.109.2-3
Severity: normal
After starting jackd with realtime priority, as a non-root user (using the
/etc/security/limits.conf trick described in
/usr/share/doc/jackd/README.Debian),
I get very unreasonable xrun numbers in the Messages log of qjackctl. E.g.:
alsa_pc
5 matches
Mail list logo
