14 Jun
2020
14 Jun
'20
4:51 a.m.
On Sat, 13 Jun 2020, rosea.grammostola wrote:
that pasuspender wasn't the solution probably. My .jackdrc is different
then the settings in qjackctl. Maybe there might be a problem then. The
.jackdrc file is updated when changing settings in qjackctl, but not
with the same -p values.
-rw-r--r-- 1 user user 56 Jun 13 20:35 .jackdrc
cat .jackdrc
/usr/bin/jackd -v -dalsa -dhw:CODEC,0 -r44100 -p128 -n2
I should clarify things a bit.
qjackctl as it comes, normally does not run jackd but rather jackdbus, it
is possible to make it run jackd instead with settings.
qjackctl does not write (so far as I know) .jackdrc directly. Rather, when
jackd is started, it writes that file as a copy of the command line used
to start jackd.
jackdbus does not use .jackrc at all.
So if you start jackd with no parameters (as you did with pasuspend --
jackd) it reads in that file instead. If qjackctl then tries to start
jackd with the settings it has, it either finds jack is already running or
tries to start jackd and fails. In either case the settings in qjackctl
would have no effect.
Anyway more stuff to study...
--
Len Ovens
www.ovenwerks.net