Subject: Re: [linux-audio-user] Jack interface peristance
From: lee (lee_AT_fallingforward.net)
Date: Sun Jun 27 2004 - 19:36:37 EEST
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
This archive was generated by hypermail 2b28 : Sun Jun 27 2004 - 19:30:00 EEST