7 Jun
2008
7 Jun
'08
8:21 p.m.
Fons Adriaensen wrote:
On Sat, Jun 07, 2008 at 06:56:15PM +0100, Rui Nuno
Capela wrote:
i guess the question is not about whether it's been difficult, but more
like it has never been thought out in the first place. qjackctl was
never meant to control more than the "default" server and that's the
bare truth i'm afraid ;)
and now that you ask, i admit this is probably the first time i consider
having multi server support in qjackctl :)
ah, maybe in a near future, when the current legacy design ashes get
buried and a new one raises from the emerging jack control interface,
which is already making strides in the jack2 svn underground, i presume :P
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
how did you, assuming that you have some solution
of your own, come to have
several qjackctl instances each one running against its own jackd server,
beyond the default that is?
I have no solution - qjackctl doesn't accept a server name option.
But I'd expect an upgrade to solve this problem rather than confirm
it. Would adding the code to accept a server name have been more
difficult than whatever was necessary to make it detect another
instance and quit ?