On Thu, 07 Jul 2011 11:20:32 +0200, rosea grammostola
you could try the "refresh" button instead...
as said above, is seems phasex takes a lot of time to start and then
stabilize its jack client ports for connections, so that it might not be
available promptly after qjackctl session manager launches it. although
qjackctl does wait a little while (+200ms) before actually restoring
connections but phasex might take more than longer... :)
there's where "refresh" button comes into play: to refresh/restore all
the previously failed connections, signaled with some red/white cross
tiny icons on qjackctl session tree-list view. got that?
> The problem with a2jmidid I reported a while ago, was because
meanwhile you could get away with a2jmidid as a
real-permanent-infrastructural-client (!) that is always started right
after jackd, being the usual candidate to be included in a
qjackctl/setup post-startup script.
rncbc aka Rui Nuno Capela
Linux-audio-dev mailing list