8 Jun
2008
8 Jun
'08
6:06 p.m.
Justin Smith wrote:
On many occasions I run more than one qjackctl with different servers.
I wrote a jack client that connects to multiple jack servers as a
"bridge". The trick with multiple qjackctls is to use the command
line, and type "DEFAULT_JACK_SERVER=usb qjackctl&
DEFAULT_JACK_SERVER=builtin qjackctl", and then hand configure each
instance to use the proper settings (auto-start should be off, of
course). Past releases of qjackctl work just fine for this purpose.
The DEFAULT_JACK_SERVER environment variable is used directly in the
jack libraries even if a client does not code in any support (there is
a small chance I have the environment variable wrong, I am pretty sure
it is DEFAULT_JACK_SERVER, I am using a friend's computer at the
moment).
I never figured out how to deal with the huge latency and xruns with
the jack bridge program, so it has not seen the light of public
release.
Please do not remove this functionality, I find it useful, even with
the buggyness of bridging between jack servers.
omg. anyway it's kind of late for that. you can avoid using this last
qjackctl release, it won't work with this setup anymore
however, i'll be your friend :) and lend this patch to let it work for
you; please test and report
btw, JACK_DEFAULT_SERVER is the variable name.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org