If you find this article contains errors or problems rendering it unreadable (missing images or files, mangled code, improper text formatting, etc) please contact the editor so corrections can be made. Thank you for helping us improve this resource
So, What Exactly Is OpenAL?
OpenAL is a (smallish) API that is designed to aid cross platform development, specifically in the area of sound and music. It is designed to be very simple at the expense of (personally speaking) functionality e.g. Panning is not supported (though some people would claim that today's 3D games would rarely, if ever, use features like that), though through clever coding, it is possible to simulate all the missing features
Its style is influenced by OpenGL, in regards to function / variable name layout, type definitions etc. so any seasoned OpenGL coder will easily be able to find their way around, but even to novices, it is simple and easy to understand (even the docs are helpful!).
Okay, now you know a little about it, let's see how to use it!
Where Can I Get My Hands On It?
Of course, the first thing you need to do is actually get the OpenAL SDK. You can do this by going to www.openAL.org . It's only about 7MB, so it shouldn't take that long to do. When you've installed it (for the sake of this article, I installed it at C:\oalsdk), have a quick look at the docs and the examples to see how simple it is to use.
What we need to do first is to set up OpenAL so we can actually use its feature set. This is extremely simple to do:
// Init openAL
// Clear Error Code (so we can catch any new errors)
That's it, now we are ready to use it!
Sources, Buffers and Listeners
Before we carry on, I'll explain the main concept behind OpenAL. The API uses 3 main components: sources, buffers and listeners. Here is a quick explanation of each -
Sources: A source in OpenAL is exactly what it sounds like, a source of a sound in the world. A source is linked to one or more buffers, and then asked to play them. They have position and orientation in the world, as well as velocity, for doppler effects.
Listener: A listener is (simply put) the ears of the world. It is generally set at the location of the player, so that all sounds will be relative to the person playing. This could be the actual camera location, or some other random position, whatever you want…
Buffers: Buffers are exactly like any other kind of sound buffers you may have used. Sound is loaded into the buffer, and then the sound in the buffer is played. The thing that differs from normal is that no functions directly call the buffer. Instead, they are linked to a source (or multiple sources) and then the sources themselves play, playing the sound from the buffers in the order that they have been queued
Okay, now that we know about the things that make OpenAL what it is, how do you use them? Well, read on…
How Do We Create What We Need?
The first things we should create are buffers, so we can actually store the sound we want to play. This is done with one simple call
All this does is create however many buffers you wish, ready to be filled with sound. The error checking is there for completeness.
The buffers do not need to be created at the start of the program; they can be created at any time. However, it's (in my opinion) neater if you create everything you need when you start. Of course, this isn't always possible, so create them in exactly the same way if you need to.
This loads in the file we have requested and fills in the given the data. Again, the error check is there for completeness. Note though the call to alDeleteBuffers(…). Even though it has failed, we need to clean up after ourselves, unless of course we want memory leaks ;)… There is also a function (alutLoadWAVMemory(…) ) that lets you load the data from memory. Take a peek at the documentation for notes on that one.
Now that we have loaded in the sound, we need to fill up one of the buffers with the data.
The above piece of code creates all the sources we need. This is exactly the same procedure as alGenBuffers(…), and the same rules apply. It is common to have far more sources than buffers, as a buffer can be attached to more than one source at the same time. Now that the source is created we need to attach a buffer to it, so we can play it…
Attaching buffers to sources is again very easy. There are two ways to do it: One way is to attach a single buffer to the source, whereas the other way is to queue multiple buffers to the source, and play them in turn. For the sake of this article, I'm just going to show you the first way.
This takes the buffer and attaches it to the source, so that when we play the source this buffer is used. The function alSourcei(…) is actually used in more than one place (in that it is a generic set integer property function for sources). I won't really go into this here, maybe another day.
Now that we have set the source and buffer, we need to position the source so that we can actually simulate 3D sound. The properties we will need to set are position, orientation and velocity. These are pretty self explanatory, but I'll mention velocity a little. Velocity is used to simulate a doppler effect. Personally, I can't stand doppler effects so I set the array to 0's, but if you want the effect, the effect will be calculated in respect to the listener's position (That's coming up next!)
Okay to set these values, you use one simple function.
This function is similar to the alSourcei(…) function except this is a generic function to set an array of floats as a source property, where ALfloat *values will be an array of 3 ALfloats. So, to set our position, velocity and orientaion we call :
These variables default them selves to 0 if you do not set them, although it is more than likely that you will. I haven't included it here, but it is best to check for errors in the standard way, because it's a good idea to catch them as they happen.
Okay, that is a source set up, now we need one more thing - the Listener.
As I said before, the listener is the ears of the world, and as such, you can only have one of them. It wouldn't make sense to have more than one, as OpenAL wouldn't know which one to make the sounds relevant to. Because there is only ever one, we do not need to create it, as it comes ready made. All we have to do is set where it is, the direction it is facing and its velocity (again for doppler effects). This is done in exactly the same way as sources with the one function
This works in exactly the same way as alSourcefv(…) and alSourcei(…) except it works on the listener. As I said, the listener comes ready made; you do not have to specify it. To set the position, orientation and velocity call:
Again, it will be a good idea to check for errors. One thing to note here is that in this case, orientation is an array of 6 ALfloat's . The first three define its look at direction, while the second three define the 'up' vector. Once this is done, everything is finally set up (It wasn't that hard was it?). Now we can get down to the thing we are all here for: Playing the sound at last
The Hills Are Alive, With The Sound of Music (!)
Yup, that's it. That's all that is required to play your sample. OpenAL will calculate the volume regarding the distance and the orientation. If you specified a velocity for either sources or listeners you'll also get doppler effects. Now that it's playing, we might need it to stop playing…
Or reset it to the start of the sample…
Or pause it…
To unpause it, just call alSourcePlay(…) on the sample.
've rushed through those, but they really are that simple. If you have a look at the OpenAL Specification and Reference document, on page 32, it will tell you exactly the actions that will happen if you call these functions on a source, depending on its state. It's simple enough, but I'm not going to go into it now.
That's all you need to do to get OpenAL up and running, but what about shutting it down?
Shutting It All Down
Shutting down is even easier than it was to set everything up. We just need to get rid of our sources, buffers and close OpenAL.
This will delete all the sources in that array of sources. Make sure you have deleted all of them before you call the next line.
And that's it. OpenAL is now shut down and you can carry on with what ever you want to do next
As this is the first article I have written, I hope it is of some use to at least one person. There's lots more to OpenAL, but this simple how-to should easily get you set up so you can look at the more complicated features (if there are any) of the API.