>Jack has some infrastructure (cvs, mailing lists, home page, >documentation, etc.) that permits to track its evolution?
it should have all these things. alas, with the current availability of time, plus the impending uncertain future of SourceForge, its not clear how best to go about this. Are you volunteering? >I ask that because from your words it seems something like Klein bottle: >it's undistinguishable what's inside and what's outside. > >Here I've laaga-0.2.3.tar.gz, but it seems a lot incomplete to me. Yes, its incomplete. It can handle audio streaming between clients and h/w, and shows the basic infrastructure as well as proving that the timing works. But there are simultaneously bugs and areas that need careful thought, such as how to get shm regions to be guaranteed to be at the same address in every client. My basic plan is to do more work on it when I convert Ardour to use it rather than AudioEngine. This will act as a suitable inducement for me to work out the problems and finish it off. --p _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
