On Tue, Aug 13, 2002 at 12:23:28 +0200, günter geiger wrote: > Actually I think for output only applications you could get off without a > redesign. Just write your data to a buffer and wait until the process() > fetches it. This will introduce a buffer copy, but the overhead is minimal > and you can happily play into your favourite soundeditor. (Which is what > we want).
True, but I think this is not ideal. The jack (ASIO, CoreAudio etc.) model has some advantages in app design, so I think it is better to change the model where possible. Plus, as you said, there is an additional copy. That said people have used this technique to port apps for that do duplex too, and I'm not sure what the best model would be if you wanted to support open/read/write and jack style i/o in the same app. Port Audio manages this I believe, I'm not sure what its API is like. - Steve
