16 Jun
2010
16 Jun
'10
10:27 a.m.
On Wed, 16 Jun 2010 09:01:58 +0100, Rui Nuno Capela wrote:
fwiw, the retry logic is there since dawn. i can assure you it's been
there for half a decade now ;) it's there for making sure qjackctl
connects
to the starting jackd server as a client of its own.
indeed, this logic is some kind of a leftover from the early days. when
machines were slower (in errors per second:) and jackd had some
considerable startup overhead before stabilizing to accept client
connections.
the delay between retrials is/was even progressive ie. each retrial
takes
a bit longer then the one before, but that's now
irrelevant i'm afraid
;)
the retrial code path will be scrapped asap. the only way for you to
avoid
qjackctl being stalled due to a (very) slow jackd
startup is now giving
it
a slack via the start delay configuration setting (cf
Setup/Settings/Start
Delay).
commited to svn trunk (qjackctl 0.3.6.28+)
- Client connection retrial logic scrapped. Being a leftover
from early ages, when machines were slower and JACK server
startup times were longer... now, if it can't connect first
time as client, it will tear down the server whether it's
starting up still or not at all. (cf. Setup/Settings/Start
Delay for the rescue).
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org