Thanks for sharing. Looks nice! A question: I see that the write callback supplies a minimum and maximum number of frames that the callback is allowed to produce. I would prefer a callback that instructed me to produce a given number of samples. It is simpler and more consistent with existing APIs. Is there a reason for the minimum and maximum arguments?
And an observation: libsoundio has a read and a write callback. If I was writing an audio program that produced output based on the input (such as a reverb, for example), do I have any guarantee that a write callback will only come after a read callback, and that for every write callback there is a read callback? Thanks! Ian On Fri, Sep 4, 2015 at 9:42 AM, Andrew Kelley <superjo...@gmail.com> wrote: > libsoundio is a C library providing cross-platform audio input and output > for real-time and consumer software. It supports JACK, PulseAudio, ALSA, > CoreAudio, and WASAPI. (Linux, Mac OS X, and Windows.) > > It is an alternative to PortAudio, RtAudio, and SDL audio. > > http://libsound.io/ > > _______________________________________________ > dupswapdrop: music-dsp mailing list > music-dsp@music.columbia.edu > https://lists.columbia.edu/mailman/listinfo/music-dsp >
_______________________________________________ dupswapdrop: music-dsp mailing list music-dsp@music.columbia.edu https://lists.columbia.edu/mailman/listinfo/music-dsp
