>When can we expect LAAGA to be stable enough (API-wise) and be supported >by linux audio programs? It's the thing I've waited the most in Linux >related development, especially for the syncing capabilities it offers.
* OK, can we start calling it JACK now, or has Karl's paper done us in ? its a good question. i'm sorry that i don't have an answer right now. i believe that the API as far as it currently exists will be stable. so far, several people on the list have been enthusiastic about it; conversely Richard Furse felt that the API wasn't adequate and offered his own much more, uhm, complex API. there wasn't much comment on that, but what there was didn't seem convinced by the need for more complexity. we need to be sure about this, because it would be crazy to proceed with the current delightfully straightforward API and then find out that Richard was right, and it can handle other things. at some point soon, i need to convert Ardour to work with JACK, which will mean work on both the reference implementation and possibly some API changes. but i can't tell you precisely when that will happen. Ardour has lots going on with the editor right now, and until that reaches some reasonable point in terms of functionality, crash-proof-ness and so forth, almost nothing else is on my mind. once I *do* get Ardour ported, its my plan to convert several other small programs to use JACK, particularly RythmnLab and SpiralLoops. --p
