Re: [LAD] qjackctl & server name

On 06/08/2010 12:04 AM, Rui Nuno Capela wrote:
> On 06/07/2010 08:24 PM, Robin Gareus wrote:
>> On 06/07/2010 02:59 PM, Rui Nuno Capela wrote:
>>> On Mon, 7 Jun 2010 08:18:23 -0400, drew Roberts <zotz@email-addr-hidden>
>>> <snip>
>>
>>>> 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...
>>
>
> maybe i messed "responsive" by "responsible"
>
> anyway, the said general default jack server name is literally "default".
>
> if you start the server for instance via `jackd -n fooserver ...` then
> this server in particular will be identified by "fooserver". then you
> will only connect to it as a client if either your application program
> calls jack_client_open("barclient", JackServerName, "fooserver") or you
> have previously set JACK_DEFAULT_SERVER=fooserver to override the
> default name (which is, uh, "default").
>
> similarly, if this `jackd -n fooserver ...` server instance is already
> found running, qjackctl will connect to it iif it's launched via
> `qjackctl -n fooserver` or JACK_DEFAULT_SERVER=fooserver is properly set.
>
> nb. when qjackctl attaches on startup to an already running jack server,
> it doesn't give a damn nor matter to which device preset you have
> configured within qjackctl settings. look, a matching jackd server name
> is found already active and most probably it has been started with some
> other means than qjackctl, so devices may differ.
>

this is getting a bit OT here, but..

in my case it does not; qjackctl is already running and started jackd in
the first place, it disconnected from that jackd when changing the
driver-backend.

Then I press "start" in qjackctl again and it launches a new server
instead of re-connecting. The server-name has not changed (it's still
'default').

Reproduce:

use qjackctl to start a jackdmp on alsa hw:0
# jack_control dps device hw:1
# jack_control sm
qjackctl disconnects

Press start in qjackctl -> it launches a 2nd jackd (on hw:0).

What works is to disconnect qjackctl (but keep jackd running) before
calling jack_control. Switch the Qjackctl Preset to match the hw:1
and "press start" in qjackctl after the `jack_control sm`.

Hence the patch I sent you earlier to that makes qjackctl
react on DBUS org.rncbc.qjackctl.loadpreset int32:<preset>

robin

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Received on Tue Jun 8 04:15:01 2010