Re: [ecasound] jack and ao-remove

Me again,

On Mon, 22 Aug 2005, Pedro Antonio Fructuoso Merino wrote:

>> How about if you add another "sleep(5)" after e.command("stop")? I suspect
>> that disconnection from JACK is taking multiple seconds and that causes the
>> ECI implementation to think the engine is not responding (and producing the
> Ok, that works.
> If you want, you can add to the ecasound control guide, section "3.2.1
> Actions" or "3.2.3 Errors" the next:
> "Note: Some EIAM commands (like cs-disconnect using JACK output) take
> multiple seconds and that causes the ECI implementation to think the engine
> is not respondig. You must wait some seconds (the current read timeout is 5

I took a bit different approach and just increased the read timeout to
30secs. There's now a separate timeout for initial read() operations that
are used during eci_init(). This timeout is still 5sec, which guarantees
that serious errors (like ecasound binary doesn't start) are still noticed
right away, and not after 30secs of waiting... :)

I just committed this to CVS (not yet in any snapshot tarball).

--
  links, my public keys, etc at http://eca.cx/kv
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Ecasound-list mailing list
Ecasound-list@email-addr-hidden
https://lists.sourceforge.net/lists/listinfo/ecasound-list