[LAU] qjackctl gets confused when used through ssh -X

Rui Nuno Capela rncbc at rncbc.org
Thu Oct 29 17:51:54 EDT 2009


fons at kokkinizita.net wrote:
> On Thu, Oct 29, 2009 at 07:27:08PM +0000, Rui Nuno Capela wrote:
> 
>> well, i can put there an explicit command line option, say `qjackctl -X`
>> that will turn off the X11 display uniqueness check. additionally, i can
>> make it user configurable through the setup dialog, as usual
> 
> There is *no* rationale at all for an X11 display uniqueness check.
> It should *never* be enforced. There *may* be a rationale for not
> having two qjackctk instances trying to control the same jackd, but
> that is a compeletely different thing.
> 
> If you are going to work on command line options, *please*
> add one that allows to select the jack server that qjackctl 
> will connect to instead of just using an environment variable.
> 

okidoki :)

however, i must say there's already support for just that although
indirectly, through qjackctl presets.

in summary, you can have presets with different server paths, for
instance, one preset named as MYPRESET for which the server path is
"jackd -n MYJACK", where MYJACK will be the server name. then you can
invoke it trough the command line as

  qjackctl --start --preset=MYPRESET

right, but that only works for _starting_ servers, not to attach to
already existing ones. that would be the precise purpose of the new
command line option you're asking for (-n, --server-name=[label], sets
the default server name) perhaps, right?

please note, that's also what the environment variable
(JACK_DEFAULT_SERVER) already does as part of the jackd specification
(jack 1 at least), so the new option will be an added convenience

cheers
-- 
rncbc aka Rui Nuno Capela
rncbc at rncbc.org



More information about the Linux-audio-user mailing list