The API consists on a graph, which redirect single or multiple input Sources into a Destination. The API will offer us different AudioNodes which can be concatenated and are used to apply filters or modify the outputs of the previous ones. The graph is represented by an interface called AudioContext, which will help us to recreate the sources, the nodes and redirect the result to the destination.
Most of the nodes can be connected to a next one with few exceptions. Those nodes are dead ends, such as the Destination.
Code example for the image without sources.
Sources can be obtained in different ways, such as streaming, audio tag, oscillator, microphone, MIDI keyboards and so on. They are the entry points to the WebContext graph.
Buffers and Streams
To inject data into out nodes, we could fill Buffers of data. The buffers speed up the processing of the audio when they are fetched from the server and they can be reused from different AudioNodes.
Streams give us the possibility to have a constant flow of information. For instance, from an audio cast in a server or from the microphone in our computer.
Fetching from XMLHttpRequest
We can fetch our sources from a server and save them to buffers. We will use an XMLHttpRequest object, setting up the responseType to arraybuffer and handling the onload event.
Using the decodeAudioData method helper from the WebContext will create a buffer from the response.
After fetching the buffer, we can create an AudioBufferSourceNode and attach the buffer to it. We can use the createBufferSource helper function on the WebContext for this propose.
The method connect from the AudioNode will help us to connect the nodes between each other and to the Destination.
Modifying the previous example:
Using audio from audio tag
We can use the tag <audio> to fetch the sound we want to load. Using the createMediaElementSource helper function from the WebContext, we can create a MediaElementAudioSourceNode to load the sound.
Firstly, we need to define the audio tag:
Because the audio is based on the <audio> tag, we will be able to use the HTML controls to play, pause and stop the sound.
Creating audio from oscillator
Previously, we were loading sounds from resources. Using the oscillator, we can create different sounds based on a frequency.
The createOscillator helper function from the WebContext will return for us an OscillatorNode. There are at least two important things we can modify from the OscillatorNode:
- Frequency in Hertz of the periodic waveform.
- Type, which is the shape of the periodic waveform.
To understand more about Oscillators, we recommended visiting this page.
The interesting part of the oscillator is the combination of them to recreate sounds. In the following example, we create three oscillators with different frequencies.
The code will be very similar to the previous one — the difference being that we used 3 frequencies.
When processing sounds, it’s very important to control the volume between different inputs. We could combine sounds with different volume, fade the volume in or out and other techniques.
The GainNode helps us have extra control to the sound of other nodes. As we saw before on the oscillator example, we could have different nodes pointing to the same Destination.
Creating GainNodes between the Sources and the Destination, we can add extra control thought the volume. Use the createGain helper function from the WebContext, we can create a new GainNode.
We will connect the Sources to the GainNodes and the GainNodes to the Destination.
Supposing we have a node created from any of the examples previously created, using the gain.value attribute of this WebNode, we can control the volume.
Analyzer and visualization
One of the interesting parts on the WebAudio is the capability to obtain information in real time about a source. This could be very useful to create representations of the sound.
Using the createAnalyser helper function from the AudioContext we can create an AnalyserNode. An AnalyserNode is a WebNode that helps us obtain real-time frequency and time-domain analysis information. Check out this page to find some of the attributes we can modify for a custom analysis.
If we want to recollect the information from the analyser – which is a very common situation – we can use the createScriptProcessor helper function in order to create a ScriptProcessorNode. This node will notify, passing as a function, when new information has been processed if we connect it to the AnaliserNode.
Using these two AudioNodes, we are able to process information. Then, we could use other APIs (like Canvas) in order to create different animations. The following example will show how to obtain information and use a dummy function called showVisuals that the reader can personalize to create animations based on the audio.
Now that we know the basics of the WebAudio, take a chance to read in-depth with the official documentation. Also, here are some examples of WebAudio on the Internet.