On 06/07/2010 02:59 PM, Rui Nuno Capela wrote: > On Mon, 7 Jun 2010 08:18:23 -0400, drew Roberts <[email protected]> > <snip> >> >> 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, >> always or only if jack is currently running. >> > > it connects only if jackd is currently running.
..and if the interface the running jackd uses matches the one in the currently active qjackctl setup. qjackctl (0.3.6.22 and jackd-1.9.6) here launches a new jackd even if jackd is running but using a different interface (eg. jackd is using hw:1 and the activated qjackctl setup says hw:0) I'd like qjackctl to always connect to an existing server if the jack-server name matches (see the "two reasons for jack2" thread). Is that possible? >> In cases where it might connect on startup, must it? >> > > no. again it only connects automatically iif a (default) server is > found responsive to open qjackctl as one of its clients. It must be even more exclusive. I have a responsive default server running and qjackctl does not connect to it. Please define "responsive to open qjackctl"; It certainly responds to ardour2, mplayer, jack-rack, patchage... >> Let's say no jack is running and we start qjackctl. 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? >> > > 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. 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 which one to connect to? >> > > none atm. each qjackctl instance may only attach to one server at a > time. > > cheers _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
