Re: [QJACKCTL] multiple versus single instance

> From: Rui Nuno Capela <rncbc@...>
> Subject: Re: [Jack-Devel] [QJACKCTL] multiple versus single instance
> To: "James Warden" <warjamy@...>
> Cc: "Jack devel" <jack-devel@...>
> Date: Saturday, June 20, 2009, 8:41 AM
> James Warden wrote:
> > Hello,
> >
> > I was wondering:
> >
> > is there an option to qjackctl so that we have only
> one running
> > instance ?
> >
> > something like:
> >
> > qjackctl --single
> >
> > So next time I start it up, it will check whether
> there's already a
> > running instance and just produce a message saying
> that one instance
> > is already running (of course, the process state shall
> be examined in
> > order to determine that the running qjackctl instance
> is a sound
> > process).
> >
> > Moreover, there seems to be a side-effect to the fact
> that you can
> > run multiple instances of qjackctl. While it may be
> fine in some
> > contexts, if you close one of them, you bring down all
> the others.
> >
>
> unless you're using a pretty old and obsolete version
> (qjackctl < 0.3.3)
> you can only have one single instance running at anyone
> time (this
> applies to linux x11 only).
>
> if you start qjackctl when one is instance is already
> running it just
> quits and does nothing besides commanding the currently
> running qjackctl
> instance to start jackd immediately *iif* not already
> active at the time.
>
> there's a workaround however: setting distinct
> JACK_DEFAULT_SERVER
> environment variable lets you have multiple qjackctl
> instances alright,
> each commanding its own jackd server.
>
> wrt. one instance bringing all others down might be a
> concern: check
> whether you're not issuing a `killall jackd` on shutdown
> (see
> setup/options/scripting) ...
>
> cheers
> --
> rncbc aka Rui Nuno Capela
> rncbc@...
>