10 Jun
2020
10 Jun
'20
1:46 a.m.
Hi,
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?
Regards,
\r
13 Jun
13 Jun
12:15 p.m.
On 6/9/20 11:46 PM, rosea.grammostola wrote:
Hi,
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
5:53 p.m.
Very odd, shouldn't htop display the same as ps, which I believe is the
command line executed?
e.g.
ps -ef |grep jackd
What if you start with the same command line without qjackctl? Maybe there
is some override in qjackctl that takes precedence...
Den lör 13 juni 2020 kl 10:16 skrev rosea.grammostola <
rosea.grammostola(a)gmail.com>gt;:
On 6/9/20 11:46 PM, rosea.grammostola wrote:
Hi,
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
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
6:26 p.m.
On Sat, 13 Jun 2020, rosea.grammostola wrote:
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.
--
Len Ovens
www.ovenwerks.net
Hi,
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
8:54 p.m.
On 6/13/20 4:26 PM, Len Ovens wrote:
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.
Hi,
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 
9:18 p.m.
Am 13.06.20 um 18:54 schrieb rosea.grammostola:
On 6/13/20 4:26 PM, Len Ovens wrote:
This thread makes me confused. htop, the linux tool as I know it, just
show the command which was used to start a application, and those
include the command-line options given.
I've as well different server configurations for jackd which I could
select from the Qjackctl settings window. There is as well a setting for
nopulse pasuspender -- jackd
and, regardless which period size I choose in Qjackctl, htop will just
display the settings I've use to start jackd.
Now, when I change the period size for jackd, later, by a other
application or by command, those will surly not be reflected in the htop
view, as htop, only know about the command used to start jackd, it
simply didn't care about the actual internal settings jackd ( or any
other application, daemon, or what ever) use.
That's why I didn't get how that could be related to the use if
pasuspender --
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.
Hi,
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
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
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
14 Jun
14 Jun
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
12:35 p.m.
On 6/14/20 2:51 AM, Len Ovens wrote:
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...
I installed the git version of qjackctl, everything
looks ok now.
1414
days inactive
1419
days old
linux-audio-user@lists.linuxaudio.org
9 comments
4 participants
participants (4)
-
Hermann Meyer -
Len Ovens -
Robert Jonsson -
rosea.grammostola