The goal of the audio API is to replicate features found in desktop audio production applications. Some of the most prominent features are mixing, processing, filtering, and etc.
The web audio API has a lot of potential, and it can do awesome stuff. But first, how well is the API supported across the board?
Cool, worth digging into!
What Is the Web Audio API Capable of Doing?
Good question! Here are a couple of examples demonstrating the capabilities of the Web Audio API. Make sure you have your sound on.
The web audio API handles audio operation through an audio context. Everything starts with the audio context. With the audio context, you can hook up different audio nodes.
Audio nodes are linked by their inputs and outputs. The chain of inputs and outputs going through a node create a destination. The destination is the audio frequency we pick up with our ears.
If you’re the type of person who wants to know all the tiny details, here’s a sweet link to get you started.
If you’re more into visual learning, here’s a great introduction talk about the Web Audio — check it out!
One of the most interesting features of the Web Audio API is the ability to extract frequency, waveform, and other data from your audio source. This can then be used to create visualizations.
This article explains how and provides a couple of basic use cases. If you’re keen on learning the audio API in depth, here’s a great series.
A Glance at the API
The web audio API is relatively intuitive to understand. Here’s an abstract example of how to use the API.
Breakdown of the steps:
- We create a new
AudioContextobject by calling it with
- We bind our oscillator and volume controller to the audio context.
- We connect our oscillators and volume controller to our sound system.
- Set our frequency type and value (tuning)
- Start our oscillator — the
startmethod of the
OscillatorNodeinterface specifies the exact time to start playing the tone.
Big Potential, Room to Grow
Of course, as with all great things, there’s always room to grow and improve. Here’s some healthy feedback from much smarter people than me.
I don't know who the Web Audio API is designed for | Hacker News
Also, due to the re-decoding every time, and the asynchronous nature of such, I've now introduced a weird bug where…
Making Music With the Browser
If you’re unsure about the use cases for such API, think about all the music composition software out there that’s desktop only. Converting those desktop apps to web apps would be a very workable business idea.
Why is web better in this case? Well, for starters, you can save and close your workspace and continue from another workspace. Musicians travel a lot, so this approach would benefit artists by a huge margin.
Another example would be enhancing our user experience with sound. (Be careful not to over-do this!)
It would deliver new solutions and better experiences for visually impaired people who use screen readers for websites leading to better accessibility.
If you’re interested in staying up-to-date, the Web Audio Conf is an excellent event to take part in.
web-audio-resources - :musical_keyboard: A list of curated web audio resources
Thanks for reading, stay awesome!