On Sat, Oct 23, 2010 at 09:08:47PM +0200, Philipp ??berbacher wrote: > Just curious, did you use ecasounds jack_connect (forgot the correct > name) or the jack_connect that ships with jack? Did it take long over > net-ECI? I wonder because the little script I wrote for that task takes > a while too, which I guess would be one or two seconds for 50 > connections, most likely because there's a lot of overhead the way I do > it (lua->tcp->net-ECI(ecasound parsing)->ecasound establishing > connection). Time delay has nothing to do with Net-ECI, but has to do with jack_connect setting up and tearing down a JACK client. From Linux Audio Users: Paul Davis wrote: > > On Wed, Oct 20, 2010 at 1:37 AM, Joel Roth <joelz@xxxxxxxxx> wrote: > > > Nama could easily be modified to start 60-or-so parallel > > jack_connect processes in the background, however I'm > > curious: is there any special reason why jack_connect should > > take a long time to return? > > it creates and destroys a client per transaction. depending on server > settings, this could slow things down quite a lot. > > jack.plumbing is a better idea, since AFAIK it reads a config file and > does all the required connections from within a single client. -- Joel Roth