web audio API player
About this project
TODO: add screenshot here showing the "simple example" UI, explain that this is just an example of an UI, you can bind your own custom UI to this player and use all or just some of it's features
😔 there is almost no documentation yet (there is some, see next section below), to learn how to use this library I recommend you check out the source code of the simple player example to get started
Want to help improve the documentation or contribute to this project by improving and fixing it, then first check out the TODOs section below, maybe there is something in the list you want to help with. Any contribution, even things not listed on the TODO list are of course welcome. To get started check out the section "contributing" section below.
npm install web-audio-api-player
This player has two modes, PLAYER_MODE_AUDIO which uses the audio element to load sounds via the audio element and PLAYER_MODE_AJAX to load sounds via the web audio API. Here are some of the differences between the two:
the web audio API (PLAYER_MODE_AJAX)
- No support for streaming
- Files get loaded using fetch, the loading progress is in percent and it is a single value between 0 and 100 percent loaded
- A song has to be fully fetched before it can be turned into a buffer and hence before the playback can start
the audio element (PLAYER_MODE_AUDIO)
- Support for streaming
- Files get loaded using the audio element, the loading progress is not just a single value, it can be split into multiple parts (time ranges), so for example the start of a song from 0 to 10 percent got loaded, then there is a blank of not yet loaded data and then also the part from 35 to 60 percent has been loaded
- A song can be played as soon as a big enough portion of the sound has been loaded (what "big enough" means, is that the browser calculates how much of the sounds needs to get loaded to be able to start playing it and continue loading (streaming) what is left without having to pause the sound at some time during the play process until the end of the playback)
You might have read (like I did) a lot of outdated web audio articles which stated the web audio element lacks a lot of features the web audio API has and that hence it is not suited to create complex audio software or for example be used in games where you might want to add effects and filters to sounds.
TLDR; This is not true anymore and especially not true for this library. Yes the audio element if used as a standalone lacks a lot of features. But this library does combine the web audio element with the web audio API.
If you use this library, the difference is only how the sound (song) gets loaded (see list of differences above). If using fetch the source is a Buffer and if using the "HTML audio element" well the source is a media element. Everything that happens after is the same. This is why you can change in the player options the PLAYER_MODE, to either load the sound using fetch or load / stream it using the audio element. But this influences only how the sound get loaded (fetched), if loaded via audio element, we use the web audio API createMediaElementSource method of the audiocontext to pass it to the audiocontext of the web audio API. After feeding the web audio API with the input from the web audio element, the playback and what you do with it is being handled by the web audio API.
so which PLAYER_MODE should I use
It depends on what you intend to build.
If you build a game where you have a lot (of small sounds) that get (pre-)loaded and maybe cached but played later at some time after they finished loading, use PLAYER_MODE_AJAX. It's progress is easier to understand, because when the loading progress of the sound has reached 100% you know it can be played. To display the loading progress a simple HTML progress element is enough.
If you build a music player, use the PLAYER_MODE_AUDIO as you might to want to start playing the sound (song) as quickly as possible and don't care if it has fully loaded yet as long as the part that has been loaded is enough to play the song until the end (while the rest of it is being streamed from the server in the background). To display the time range(s) that have been loaded you could for example use a 2D canvas element.
You can create and then inject your own AudioContext
You can inject your own, if you want to reuse an existing one your app already created: ...
You can also take the one created by the library and alter it the way you want: ...
You can create and then inject your own AudioGraph (audio routing graph)
This is especially useful if you want to add your own nodes to the AudioGraph (audio routing graph). For example you may want to add an AnalyserNode or a pannerNode, delayNode or any other node that is available in the web audio API.
W3C web audio API
Support tables for audio features, caniuse: web audio API / audio element / formats ...
install the latest nodejs (if you haven't already) nodejs
install or update to the latest git version git scm downloads (During installation at the step "choosing the default editor used by Git", if like me you are using visual studio code you might want to chose the new option "use visual studio code as Git's default editor") (also if like me you are on windows, at the step "adjusting your PATH environment", ensure the second radio button option is selected "git from the line and also from 3rd-party software" to ensure git is added to the windows PATH, which will allow you to use git with any command line tool like windows powershell for example)
git clone this repository to get a local copy
git clone email@example.com:chrisweb/web-audio-api-player.git
open your favorite command line tool and go to the root directory of this repository
update npm to latest version
npm install npm@latest -g
install the dependencies
to build the distributions
- es6 module = /dist/index.js
- UMD version = /dist/index.umd.js
npm run build
in development you can use watch to rebuild every time you edit a typescript file
npm run watch
to lint the typescript files
npm run lint
you should first open a ticket and explain what fix or improvement you want to provide on the github issues page of this project (remember the github ticket number you will need it for the commit message later on)
go the github page of this project and hit the fork button
follow the instructions in the previous section "development: build", but instead of cloning this projects repository, clone your own fork of the project
git clone firstname.lastname@example.org:YOUR_USERNAME/web-audio-api-player.git
when you are done coding, commit your local changes (if your commit is related to a ticket start your commit message with the "#TICKER_NUMBER")
git commit -m "#TICKER_NUMBER commit message"
now open your forks github URL in your browser and hit the pull request button
the best way to get started is to check out the examples folder, start with simple player example
note to self: publish package on npmjs.com
login to npmjs.com
!!! before using the next the command ensure the version of your package in the package.json has been updated
publish a new version on npmjs
notes about problems I encountered during development
web audio api typings notes
As of now (25.05.2019) the web audio api typings seems to be included in lib.d.ts, so removing them from package.json:
TODOs (help wanted 😊)
- create a react example
- create a vue.js example
- create an example using the fileReader
var fileInput = document;fileInput;
- completely rewrite the sources system, where you can define multiple variants of a sound but with different codecs, app needs to check which codecs are supported by the device and choose one, use should be able to define which codec is preferred if playback support for multiple codecs is available
- implement audiocontext to close to release memory?
- feature to use the browser notification system to alert which song is being played
- instead of the ArrayBuffer use the MediaElementAudioSourceNode, make it optional to still use the ArrayBuffer
- preload AudioBuffers in indexeddb (first song, next song, current song if loop or previous is triggered ...), let the developer set the amount of preloaded AudioBuffers, remove from "cache" by least used and by date when "cache" is full
- cache songs for offline mode? indexeddb is not very big (filesystem?), check if doable because saving a playlist of songs might exhaust the free space
- some methods return a promise others don't, use promises for all to make it more consistent?
- write a documentation
- make a list of all possible errors (set a distinct code for each error)
- add a contribution guide
- write tests!!! (goal 100% coverage), add tests coverage badge
- abort the loading of the sound if the user clicks play and then pause (or stop / next / previous) before the end of the buffering process
- replace XMLHttpRequest with fetch?
- allow cross fading songs "on end" if it's the next song in a playlist (or just fade out / fade in)
- currently the "find song in queue" can't retrieve songs by queue index, is this useful anyway?
- use suspend and resume if for some time no sound was played? ... to free device resources. As suspend returns a promise, does this mean suspending and resuming takes time? if so how much time does it take, based on that information we can decide after how much time it makes sense to suspend the ctx to save device resources
- use the requestAnimation frame or the requestidlecallback instead of setInterval for playing progress callback?
- use web workers, especially for the decoding of the ArrayBuffer into an AudioBuffer, to not block the main thread while decoding?
- add shuffle mode
- add a loop song and loop queue mode (https://webaudio.github.io/web-audio-api/#looping-AudioBufferSourceNode)
- handle all error cases that are still unhandled
- add support for more codecs (flac, wav, ogg vorbis, opus, aac): also check the available codecs and defined sources, play the first one that has matches and available codec, let user define order of preferred codecs for playback
- add saucelabs browser testing and their badge browser compatibility table badge in readme
- add travis continuous integration and badge
- add improve UI style and then add a screenshot to readme of example
- add live demo (via github pages)
- for position and volume, allow to use a percentage or a value
- add hooks to the sound object for all the native source node events AudioBufferSourceNode
- add (stereo) panning
- use gulp gulp and some gulp plugins to create a clean build
- create an XMLHttpRequest library class to fetch the ArrayBuffer
- create an audio library class to create the context and decode the ArrayBuffer
- create a custom error class with message but also a numeric code
- let the user add a sound with an already fetched ArrayBuffer or even with an already decoded AudioBuffer
- create a simple example with a vanilla JS UI
- add a sounds queue manager
- add "play" sound
- add "pause" and "stop"
- add "next" and "previous"
- add set / get volume and mute
- add a loading progress callback
- add a playing progress callback
- add an onEnded callback
- play next song onEnded, add option to enable or disable automatic play next onEnded
- add change position method
- add loop queue option
- make the core player options object optional when initializing a new player
- let the user modify the audio graph, for example by adding / removíng nodes like a filter node, a panner node ...
- replace gulp with rollup as new module bundler
- use pkg.module to distribute a UMD as well as an "ES6 modules" version
- rewrite the simple example with vanilla js instead of jquery
- put the web audio API player on npm and add npm version badge / license badge / ... shields.io
- implement suspend and resume: ctx.suspend() and resume
- add an option that uses the visibility API to automatically mute and unmute a sound when the visibility changes
- rewrite how the audiocontext is created, for browser that enforce that a user interaction has taken place before a context can be running
- add option to persist the user volume choice using the localstorage
- switch from tslint to eslint with typescript-eslint plugin / parser: TSlint will be deprecated github ticket, read their blog post and then switch to ESLint