9 Feb
2013
9 Feb
'13
10:48 a.m.
Hi,
I was a long term jackd1 user and my first action on a new linux
installation (mostly using Ubuntu) was normally to remove pulseaudio as
it was badly configured and/or buggy. Things have changed and I really
started to like PA for everyday stuff. And then jackdbus came along
which together with the device reservation API and the jackd sinks
promised to make using these two things together more easy. This mostly
works fine, except for the device reservation bug in PA which is easy to
work around though:
- Make sure no audio process is actively using the soundcard you want
jackd to use
- Run pulseaudio -k
- Run jack_control start
I have noticed some issues with jackdbus though:
a] jack_control start sometimes doesn't work at all after the first time
it failed to aquire the device. A killall -9 jackdbus is in order to
restore it
b] after some hours of operation jackdbus starts to eat 100% cpu on two
of my four cores.
Are these known issues? I use Ubuntu 12.10 and jackd:
fps@mango 12:08:21 .../Games/Xonotic/ $ jackd -v
jackdmp 1.9.9
[...]
How to diagnose the 100% cpu thing more closely? The
~.log/jack/jackdbus.log shows nothing suspicious.
Thanks and regards,
Flo
--
Florian Paul Schmidt
http://fps.io
9 Feb
9 Feb
1:11 p.m.
On Sat, Feb 9, 2013 at 9:48 AM, Florian Paul Schmidt
<mista.tapas(a)gmx.net> wrote:
Hi,
I was a long term jackd1 user and my first action on a new linux
installation (mostly using Ubuntu) was normally to remove pulseaudio as it
was badly configured and/or buggy. Things have changed and I really started
to like PA for everyday stuff. And then jackdbus came along which together
with the device reservation API and the jackd sinks promised to make using
these two things together more easy. This mostly works fine, except for the
device reservation bug in PA which is easy to work around though:
- Make sure no audio process is actively using the soundcard you want jackd
to use
- Run pulseaudio -k
- Run jack_control start
I have noticed some issues with jackdbus though:
a] jack_control start sometimes doesn't work at all after the first time it
failed to aquire the device. A killall -9 jackdbus is in order to restore it
b] after some hours of operation jackdbus starts to eat 100% cpu on two of
my four cores.
Are these known issues? I use Ubuntu 12.10 and jackd:
Hi Flo,
I am also running Ubuntu 12.10 and using jackdbus. It is really nice
for things like playing along to youtube videos.. On my computer, I
noticed that jack does have a tendency to lockup after a while when
jackdbus is running. I had the feeling that it might be something to
do with latency, as I found it is impossible to start jack at very low
latencies with jackdbus running. I was using 128 samples which seemed
to be OK, but at that latency, the lockups occurred after some time. I
tried increasing latency to 256 samples/44.1k. Following this, it
seems to operate fine (at least I have had no more dropouts), but it
is all a bit fiddly to get it to work properly, and I would probably
disable pulse if I wanted to do serious recording etc without the
mixing capabilities that jackdbus adds..
James
1:24 p.m.
Hi James,
On 02/09/2013 01:11 PM, James Stone wrote:
Hi Flo, I am also running Ubuntu 12.10 and using
jackdbus. It is
really nice for things like playing along to youtube videos.. On my
computer, I noticed that jack does have a tendency to lockup after a
while when jackdbus is running. I had the feeling that it might be
something to do with latency, as I found it is impossible to start
jack at very low latencies with jackdbus running. I was using 128
samples which seemed to be OK, but at that latency, the lockups
occurred after some time. I tried increasing latency to 256
samples/44.1k. Following this, it seems to operate fine (at least I
have had no more dropouts), but it is all a bit fiddly to get it to
work properly, and I would probably disable pulse if I wanted to do
serious recording etc without the mixing capabilities that jackdbus
adds.. James
I use very large period sizes, 1024 or even 2048. The problem of jackd
starting to eat 100% cpu occurs usually when I'm done with my current
work (recording something or fiddling around) and just leave it running
idly. Then when I return to my computer after a few hours jackd sits
there happily eating cpu. It has the side effect of heating my room, but
heating with electricity is expensive and thus I'd rather avoid it ;D
Have fun,
Flo
--
Florian Paul Schmidt
http://fps.io
4:10 p.m.
On Sat, February 9, 2013 4:11 am, James Stone wrote:
I am also running Ubuntu 12.10 and using jackdbus. It
is really nice
for things like playing along to youtube videos.. On my computer, I
noticed that jack does have a tendency to lockup after a while when
jackdbus is running. I had the feeling that it might be something to
do with latency, as I found it is impossible to start jack at very low
latencies with jackdbus running.
I haven't had that problem -p 32 r 48000 starts on my D66 with no
problems. 32 samples is pushing it for this system though, just changing
workspace is enough to give an xrun sometimes. bumping it up to 64 seems
to be enough. I am using a 10year old P4 at 2.4Ghz. In general, I have
found pulse seems to take twice the cpu that jackdbus does at the same
latency. (according to top)
I was using 128 samples which seemed
to be OK, but at that latency, the lockups occurred after some time. I
tried increasing latency to 256 samples/44.1k. Following this, it
seems to operate fine (at least I have had no more dropouts), but it
is all a bit fiddly to get it to work properly, and I would probably
disable pulse if I wanted to do serious recording etc without the
mixing capabilities that jackdbus adds..
I have found that unloading the module-jackdbus-detect module while
recording is just as effective. Pulse uses very little resources with the
PA-jack bridge unloaded. It can be reloaded when finished recording or
just pulseaudio -k
I have a script that does this... as well as a few other things (turn off
cron and other services I don't need, set CPU governor to a steady state,
etc)
--
Len Ovens
www.OvenWerks.net
4297
days inactive
4297
days old
linux-audio-user@lists.linuxaudio.org
3 comments
3 participants
participants (3)
-
Florian Paul Schmidt -
James Stone -
Len Ovens