RE: Question about OpenAl Versions

Thanks Chris for the information.  I have looked at several of the wrappers
that are supposed to make OpenAL easier but they either don't compile or
they are way harder than using OpenAL as it is.  Thanks for your time and
effort.

You commented below about an alsoft.conf file.  I am currently working on
Windows platforms and do not have those files, at least I don't see them
anywhere.

I did write a WaveFile class to create and playback wave files but I am
having problems with ausio that I capture to a wave file.  Playback of
downloaded wave files all sounds clean but there is a crackle at the
beginning of the files I create.  After that the audio seems to be ok.  I
sent a sample to the forum but it was apparently blocked because I did not
see the usual posting notice.

Bruce

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Chris Robinson
Sent: Sunday, November 14, 2010 9:35 PM
To: [email protected]
Subject: Re: [Openal] Question about OpenAl Versions

On Sunday, November 14, 2010 4:34:49 pm Bruce Clay wrote:
> When I looked through the code in the version before OpenAl soft I notice
> several files that are not in the soft version such as alc_backend_wave
and
> al_ext_mp3.  Are there license issues with these files or will they be
> incorporated in a future version?

OpenAL Soft is based on the OpenAL-Windows code base instead of
OpenAL-Sample. 
The backends were redone from scratch, and the wave backend is in wave.c.
But 
you need to specify the output file, using ~/.alsoftrc or 
/etc/openal/alsoft.conf, to make it work:

[wave]
file = output.wav  # Careful, this will overwrite existing files!

Then it should be enumerated and openable like the rest. Capture from a wave

file is not supported, though.


As for the MP3/Vorbis extensions, the biggest thing is that they're not very

practical. Compressed formats (and long sounds in general) are better suited

to streaming, so loading them fully into a buffer would be wasteful. Also,
an 
app couldn't rely on the extensions being available, so it would need a 
fallback method to decode them anyway.

> There are several files in the OpenAL-Sample/test directory that if the
> code is still valid answer a lot of developer questions.  Some of them use
> alut which I could not get to work on Windows 7 but they still seem to
> have a lot of the basic capabilities.

Not all of the tests are still "valid"... many seem to rely on extensions
that 
are no longer supported, and are buggy (using wrong orientation values,
leaks, 
etc). I have been meaning to write new examples and tests, though.
_______________________________________________
Openal mailing list
[email protected]
http://opensource.creative.com/mailman/listinfo/openal

_______________________________________________
Openal mailing list
[email protected]
http://opensource.creative.com/mailman/listinfo/openal