[Openal-devel] Loopback API design question
erik at ehofman.com
Tue Feb 28 06:47:12 PST 2012
On Tue, 2012-02-28 at 03:26 -0800, Chris Robinson wrote:
> The idea here is that it would allow an application to render the audio at its
> own pace and write it out to where it wants. This could, for example, be as
> fast as possible to an audio codec (to compress to an on-disk file or
> something), or to its own audio device at the device's speed (if it can't or
> doesn't want to use OpenAL's device handling for some reason).
I think that specifying ALC_REFRESH to 0 to be ast fast as possible
would solve this problem.
> If the application has to have an output device open, then has to wait for
> audio to be generated before it can do anything with it, it wouldn't work as
> well for that purpose.
In your proposal the caller will also have to wait for the data to be
available in alcRenderSamplesSOFT.
To me both implementations are not mutually exclusive in that one would
provide more functionality over the other. I just think that using the
alcCapture functions would be a bit cleaner.
More information about the Openal-devel