Hey Eric, great job!
We tried going with openal some time ago with a custom wrapper.
It was fun to use, expecially fro osx and ios, we got it running on
linux, but in the end the whole thing had to stop because on windows
there’s the usual driver mess.
Some drivers worked fine, creative ones cheated claiming they
supported openal but missed many feature, and some others just didn’t
So on Windows, there are two basic solutions. Use Creative’s drivers
or use OpenAL soft. Early on, Creative had some issues (though all the
implementations had issues). I would hope they are resolved now. I
don’t hear many complaints on the OpenAL mailing list anymore. OpenAL
Soft is your alternative. People who like bundling OpenAL with their
app and avoid installers seem to gravitate towards OpenAL soft.
OpenAL soft is the only game in town on Linux. But the maintainer,
Chris Robinson, is very active on it and it seems like a solid
distribution to me. He is usually the first to propose new extensions
to OpenAL and implement them.
How does ALmixer handle all this? does it have a fallback driver? an
automatic software render?
ALmixer does very little. (It actually has some legacy stuff in the
code base which tries to do too much…you might see esoteric
references to Loki, Creative, and Nvidia which are pretty much
obsolete now.) At one time, I supported a way to pass custom settings
to the Init, so if there was an implementation specific way of setting
things, you could try to do this. Maybe the Creative implementation
still lets you control things? But I kind of dropped this mess after
OpenAL 1.1 was ratified. If you have a specific things you need to do,
I’m willing to listen. My hope is that OpenAL 1.1 is consistent enough
that you won’t need to care any more, at least w.r.t. what ALmixer
needs to do.
another question is SDL_sound and or ALmixer going to be a replacement
for SDL_mixer in the next years?
ALmixer probably won’t replace SDL_mixer from a policy point. However,
if people just start using ALmixer entirely, it could happen
unofficially that way. But there are a lot of milestones that need to
happen before that ever happens. (Testing, better examples, better
documentation, binary releases, etc.) And I don’t think there is any
plan to retire SDL_mixer. (I am not involved in that decision process.
ALmixer is entirely my own crazy invention and is not coordinated with
official SDL in any way.)
A long time ago, it was planned/expected that SDL_mixer’s decoder
backend would be replaced to use SDL_sound. However, that still hasn’t
-EricOn 10/28/10, Vittorio Giovara <vittorio.giovara at gmail.com> wrote:
Beginning iPhone Games Development