linuxaudio.org

On Mon, 7 Jun 2010 08:18:23 -0400, drew Roberts  wrote:

quoted text
>>>> JACK_DEFAULT_SERVER environment variable might be your (only) friend

>>>> here :)

>

quoted text
> Hold on a second. Let me try walking through this.

>

> We start qjackctl. Does it connect to a jack server at this point? If

so,

quoted text
> always or only if jack is currently running.

> 

it connects only if jackd is currently running.
> In cases where it might connect on startup, must it?

quoted text
>

no. again it only connects automatically iif a (default) server is found

responsive to open qjackctl as one of its clients.
> Let's say no jack is running and we start qjackctl.

quoted text
> Let's say it doesn't connect to jack at this point.

i does not.
> Could there not be a setup option to indicate what -n indicated now?

quoted text
> 

qjackctl -n command line option is just convenient for you to start jackd

server with that precise server name and let qjackctl connect immediately

to it as client to that same server.
> Let's say multiple jacks are running and we start qjackctl.

quoted text
> Is it possible to discover that multiple jacks are running?

nope. qjackctl will only "see" the default jack server or the one named by

JACK_DEFAULT_SERVER environment variable at the time qjackctl is launched.
> If so, would it be possible to allow a choice from within the gui as to

quoted text
> which one to connect to?

> 

none atm. each qjackctl instance may only attach to one server at a time.
cheers

--

rncbc aka Rui Nuno Capela

rncbc@rncbc.org

_______________________________________________

Linux-audio-dev mailing list

Linux-audio-dev@lists.linuxaudio.org

http://lists.linuxaudio.org/listinfo/linux-audio-dev