On Wed, 17 Aug 2005, Pedro Antonio Fructuoso Merino wrote:
> e.command("start");
> sleep(5);
> e.command("stop");
> e.command("cs-select play_chainsetup");
> e.command("cs-disconnect")
> std::cout << "FIN" << std::endl;
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 errors you quoted). The current read timeout is 5 secs.
> e.command("stop");
> e.command("cs-select play_chainsetup");
> // e.command("cs-disconnect");
> and all work well.
This would suggest that my above theory is correct.
-- 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-listReceived on Sun Aug 21 20:15:09 2005
This archive was generated by hypermail 2.1.8 : Sun Aug 21 2005 - 20:15:09 EEST