[nama] Re: e: Pushed changes to master

Excerpts from Joel Roth's message of 2010-10-24 09:47:10 +0200:
> On Sun, Oct 24, 2010 at 09:31:40AM +0200, Philipp ??berbacher wrote:
> > Excerpts from Joel Roth's message of 2010-10-24 02:17:14 +0200:
> > > 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. 
> > 
> > I wouldn't say it has nothing to do with it, just that jack_connect is
> > another reason why it's slow. tcp and parsing on the ecasound side of
> > thing certainly also takes its time, and ecasound is parsing quite a bit
> > for every connection (as everything that goes through net-ECI goes
> > through the parser). Anyway, it shows that my reconnect thingy is really
> > badly designed :)
> 
> I'm glad your script isn't perfect. Would hate to see you
> denied a learning opportunity. :-)
> 
> Jack.plumbing offers a convenient solution for Nama. Maybe
> it will work for you, too. 
> 
> Best,
> 
> Joel

Maybe, but my project is currently pretty much on hold. I think I start
to suffer from second-system-syndrome. I want to start over and do
everything right the second time, but it won't ever become usable :)

This time I'm aiming for lua-ecasound bindings and some C code, or
writing my own backend altogether :)
Obviously it will take ten years to become usable at all.

Regards,
Philipp


Other related posts: