On Sunday 01 June 2008 02:19:40 am Erik Hofman wrote:
> I've created an ima4 adpcm codec and support for the wav file reader of
> alut:
>
http://ehtw.speedlinq.nl/emh/alut_ima-adpcm.diff>
> I've tested this code for both mono and stereo compressed files.
Thinking about it, I wonder if it would be a good idea to test for the
AL_EXT_IMA4 extension, and pass the data to OpenAL without conversion (at
least when dealing with the alutCreateBuffer* functions).
And I'm curious about what to do with the alutLoadMemory* functions. The ALUT
spec says the function will return data in a "standard OpenAL format", but
never lists any formats or expands on what it means. Should this only be
basic formats (mono/stereo 8/16 bit PCM only), core-only formats (whichever
are supported by the AL version), or any formats the implementation is
capable of handling (determined from core version and availability of known
extensions)?
If it means core formats, I don't see the harm in supporting extensions as
well, since they can similarly add formats the app may not recognize (and as
such, an app couldn't rely on the returned data being a known format). But if
it means only basic formats, that makes the function much less desirable if
trying to use compressed formats.
_______________________________________________
Openal-devel mailing list
Openal-devel@...
http://opensource.creative.com/mailman/listinfo/openal-devel
