jvalenzu at infinite-monkeys.org
Mon Aug 22 10:08:02 PDT 2005
The purpose that the alut functions originally served is not really
necessary anymore. In general I prefer extension format tokens as
format parameters to alBufferData, but (as you aalude to) for most
wave files the loading code would be very general.
On Aug 22, 2005, at 12:20 AM, Ryan C. Gordon wrote:
>> 3) I *could* bite the bullet and write my own WAV unpack code and
>> stuff that
>> data into an alBuffer myself - but that's the very last thing
>> I should
>> have to do when I start out with OpenAL. WAV files are certainly
>> a de-facto
>> standard - but they are a pain to read because there are multiple
>> layers of
>> headers that often contradict each other...it's a terrible format
>> to have to
>> parse yourself.
> Is there a Windows Bitmap loader in GLUT that I'm not aware of?
> What we really need, short term, is about 100 lines of public domain C
> code that creates an AL buffer from an uncompressed wave file, and you
> are welcome to drop it into your application.
> Long term, we need to stop complaining about how screwed up ALUT is
> (because it actually IS, after all) and actually take steps to do
> something about it.
> openal mailing list
> openal at opensource.creative.com
More information about the Openal