[Openal-devel] mixaudio question
Sven.Panne at aedion.de
Sat Oct 22 07:30:16 PDT 2005
Am Samstag, 22. Oktober 2005 15:03 schrieb Ryan C. Gordon:
> However, let's say that AL_EXT_vorbis isn't available, and I feed a
> Vorbis file to ALUT...if it has libvorbis support behind the scenes,
> it'll presumably decode the entire file to feed it to alBufferData() and
> return the AL buffer to the caller.
> The app, in the same scenario, can see that AL_EXT_vorbis doesn't exist
> and instead opt to use buffer queueing to keep the memory footprint down.
> Is this an intentional tradeoff in the name of simplicity?
Yes, it is, and I think it is good enough for most small demos and
medium-sized applications. If we come up with a reasonable streaming API, we
can do better, of course. But even in that case I think we should leave the
current API entries in ALUT, they are very straightforward to use and
understand, which is very important IMHO.
More information about the Openal-devel