13 Jun
2020
13 Jun
'20
9:22 p.m.
On Sat, 13 Jun 2020, rosea.grammostola wrote:
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.
--
Len Ovens
www.ovenwerks.net
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
On 6/9/20 11:46 PM, rosea.grammostola wrote:
Just a guess, but I expect Jack was already running at -p 64. The
second jackd start at -p 128 then failed. Try killall -9 jackd before
using qjackctl to start.
I've set jackd to -p 128 in qjackctl (0.6.2
Debian), but jackd shows
up in htop and Carla with -p 64. Huh?
Could this be something related to using a
usb card? Htop always
displays -p 64 here, whatever setting I've in Qjackctl