27 Jun
2004
27 Jun
'04
8:40 a.m.
This is not just XMMS but most anything. After the client has terminated (or
one thinks it had terminated), the connection or connection points persists
in qjackctl. The program is now unstable and jack must be manually killed.
Xmms instances remain in memory and must be killed.
Jackrack exists OK but its connection points remain
Aviplay (jacklaunched) seems OK
Realplay10 (Helix), connections persist .....
How might on fix all this up. Is there a nicer way to restart jackd than to
find the PID, kill it and restart qjackctl?
27 Jun
27 Jun
1:51 p.m.
Last Sunday 27 June 2004 11:31, David Baron was like:
This is not just XMMS but most anything. After the
client has terminated
(or one thinks it had terminated), the connection or connection points
persists in qjackctl. The program is now unstable and jack must be manually
killed.
[...]
How might on fix all this up. Is there a nicer way to restart jackd than to
find the PID, kill it and restart qjackctl?
I'm frequently resorting to scripts to start my regular jack sessions, in
which
killall foo
foo -bar
works for most things. There's a fairly simple way of scripting a PID 'search
& destroy' mechanism, I haven't quite got frustrated enough times to do it
yet ;-] but any suggestions of a more graceful way to do it appreciated.
cheers
tim hall
2:46 p.m.
David Baron wrote:
This is not just XMMS but most anything. After the
client has terminated (or
one thinks it had terminated), the connection or connection points persists
in qjackctl. The program is now unstable and jack must be manually killed.
This happens to me also but more infrequently than you. I think it may
be caused by how the specific application uses the jack interface and
not necessarily jack it's self. You should first start be contacting the
apps authors.
Xmms instances remain in memory and must be killed.
Jackrack exists OK but its connection points remain
Aviplay (jacklaunched) seems OK
Realplay10 (Helix), connections persist .....
How are you getting Helix player to connect to jack?
How might on fix all this up. Is there a nicer way to
restart jackd than to
find the PID, kill it and restart qjackctl?
That's pretty much how every single process is dealt with in the unix
world. I believe qjackctl automates this with the "stop" button.
-lee
7483
days inactive
7483
days old
linux-audio-user@lists.linuxaudio.org
2 comments
3 participants
participants (3)
-
David Baron -
lee -
tim hall