Hello, we are finally getting close to reaching the original goals set for JACK. The last big step has been the transport interface (to refresh your memory, take a look at the initial JACK/LAAGA use-scenario [1]). Thanks to Jack O'Quin's recent efforts, JACK now finally has a transport interface (and implementation) that fulfills all the requirements, and one that makes it possible to realize the example case [1]. Now at this point we'd _really_ appreaciate your input. If you are short of time, at least take a look at our requirements list at the start of the design doc: http://www.joq.us/jack/refman/transport-design.html The big questions are: 1. Is this API sufficient for your application? If not what is missing and/or wrong? 2. Do you plan to add support for JACK transport to your app? If not, what is the main reason not to (no interest, not useful for your app, you prefer other solutions, etc)? In addition, comments regarding interface and implementation details are also welcome. [1] http://www.eca.cx/laaga ---------- Forwarded message ---------- Date: 13 Aug 2003 22:08:09 -0500 From: Jack O'Quin &lt;joq(a)io.com&gt; To: jackit-devel(a)lists.sourceforge.net Subject: [Jackit-devel] CVS commit [0.77.0] new transport BETA test The new transport interfaces are ready for beta testing. Bring on your applications and give it a try. We will likely want to tweak a few things as problems are discovered. So, please don't release any applications that depend on the new API until the beta test is finished and we cut a new JACK release. But, the design seems stable right now. The reference manual is still at... <http:www.joq.us/jack/refman> If you don't want to wait for CVS to catch up, here's a tarball... <http:www.joq.us/jack/jack-audio-connection-kit-0.77.0-beta.tar.gz> Highlights... * new minor version, API version and protocol version -- to distinguish beta test level from earlier snapshots -- source compatible with recent 0.76 snapshots -- transport API not binary compatible: must recompile * functional test complete (except internal clients) -- if you have an internal transport client, try it -- it might work, but I still have no test cases * jackd -v option (--verbose) now prints useful transport state change information for debugging JACK and clients both * includes Bob Ham's makefile fix for the jackrec example client -- Jack O'Quin Austin, Texas, USA