13 Jun
2020
13 Jun
'20
10:46 p.m.
On 6/13/20 7:22 PM, Len Ovens wrote:
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
On 6/13/20 4:26 PM, Len Ovens wrote:
"pasuspender -- jackd" That would start jackd using $HOME/.jackdrc as
the commandline. Then qjackctl would not start using it's settings
because jack is already running. Now that qjackctl has been able to
start jackd at least once, those settings should have been saved to
$HOME/.jackdrc so adding the "pasuspender -- jackd" back in would
_appear_ to work. Pasuspender shouldn't be needed anyway unless you
are running with no dbus running. Dbus running or not seems to be a
personal choice even with no X running. On Sat, 13 Jun 2020, rosea.grammostola wrote:
When I run jackd from terminal, htop displays the right -p setting.
In Qjackctl, not matter which -p setting, htop always shows -p 64
Wait... It seems to have to do with the Server suffix setting I have.
pasuspender -- jackd
When I remove it, htop shows the right -p