>I don't agree with Paul that the latency.c test program is not a good >example for testing and showing the capture -> process -> play circle >required by some applications.
applications that do this will need to be multithreaded if they have any UI at all (i.e. anything involving real-time control of the programs operation, graphical or otherwise). this introduces a host of complications that significantly overshadow whats involved in setting up the basic i/o loop. latency.c is, in that sense, a toy program. toy programs are fun, but they are not good demonstrations of how to write applications that do more interesting things. i consider it absurd that in a day and age where developers for OS X can use the CoreAudio API, and developers for Windows and MacOS [0-9] can generally focus on writing plugins, that audio developers for linux have to be thinking about the intricate details of the ALSA device-centered APIs. i will work as hard as i can to get JACK into a more polished condition so that this absurdity can be ignored by people who want to work in ignorance of these sorts of details. --p _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel