On Sat, February 9, 2013 1:48 am, Florian Paul Schmidt wrote:
There is a real fix in the pipe line... not sure when it will get into
releases. I find:
pasuspender --sleep 5 & ; jack_control start
Will allow me to start jackdbus even while pulse is streaming. Actually I
use pasuspender from qjackctl to do the same thing.
> I have noticed some issues with jackdbus though:
jack_control exit works for me. This is part of the bug above, when
jackdbus fails to get the device, the jackd part dies but the dbus part
doesn't (it seems, I don't know the code well enough) It would be
interesting to compare this behaviour with jackd2.
> b] after some hours of operation jackdbus starts to eat 100% cpu on two
I have left jackdbus running for at least 5 days and have not seen this
show up. PA has been used during that time (audacious and fire fox) as
well as other jack clients. I would be interested to know if running jackd
instead of jackdbus is the same or different.
There are some patches on the way for jack2 in ubuntu as well. (in testing)
I am using the alpha 13.04 on this machine and 12.04 on another.
joe@studio1304:~$ jackd -v
The plan is that once the jackd patches are tested they will be SRU to
12.04 and 12.10.
Linux-audio-user mailing list