Sound processing: Should I use DirectSound or directly Win32 APIs

Both DirectSound and the Wave API ultimately give you buffers filled with audio data that you can process. The size of these buffers can be varied, but realistically you will need to keep latency to less then 10mS for useful realtime processing. This means processing data within 10mS of it arriving at the buffer, minus the time between it arriving at the audio hardware and getting to the buffer, which will depend on the driver. For this reason I would recommend processing no more than 5mS of data at a time.

The main architectural difference between the two is that with DirectSound you allocate a circular buffer which is then filled by the DirectSound audio driver whereas the Wave API takes a queue of pre-allocated WAVEHDR buffers which are filled, returned to the app and then recycled. There are various notification methods for both APIs, such as window messages or events. However, for low-latency processing it's probably advisable to maintain a dedicated streaming thread and wait for new data to arrive.

For various reasons I would recommend DirectSound over the Wave API for new development - it will certainly be easier to achieve lower latency.

Whichever method you choose to do the capturing, once you have your data you simply pass it to your processing algorithm and wait for the next buffer to be ready. As long as you can process the data faster than it arrives then you'll have your (pseudo) real time analysis.

There are also alternative APIs that may be more suitable. Have a look at ASIO, Kernel Streaming (for XP only - I wouldn't bother) and, new in Vista, the Core Audio APIs.

If you run bin/startup.bat, then Tomcat should launch in the background and stdout/stderr should be redirected to logs/catalina.out. If, instead, you run bin/catalina.sh run (note the additional command-line argument "run"), then Tomcat should run in the console and all stdout/stderr should be displayed there.