StartAudioContext starts the Web Audio API's AudioContext on an explicit user action.
According to the Apple's documentation:
On iOS, the Web Audio API requires sounds to be triggered from an explicit user action, such as a tap. Calling noteOn() from an onload event will not play sound.
StartAudioContext listens for the first non-dragged touchend or mouseup event on any of the given elements, then triggers a silent AudioBuffer which will start the AudioContext if it isn't already started.
Choose one:
- download the js
npm install startaudiocontextbower install startaudiocontext
//pass in the audio context
var context = new AudioContext();
//on iOS, the context will be started on the first valid user action on the #playButton element
StartAudioContext(context, "#playButton")StartAudioContext(AudioContext, (Elements), (Callback)) => Promise
StartAudioContext will monitor the passed in AudioContext and resolve the promise and/or invoke the passed in callback when the AudioContext.state === 'running'.
The second argument can be an Element, Selector String, NodeList, jQuery Element or an Array of any of those. An event listener is bound to any of the passed in elements which will listen for a valid touch events to trigger a silent AudioBuffer which will start the AudioContext.
StartAudioContext(audioContext, '#button', function(){
//audio context is started
})If no element is passed in, it will bind to document.body.
The third argument is the callback to invoke when the AudioContext has started.
StartAudioContext returns a promise which is resolved when the AudioContext state is 'running'.
StartAudioContext(audioContext).then(function(){
//context is started
})If you're using StartAudioContext with Tone.js or any other library which creates an AudioContext, pass in that AudioContext instead of creating a new one:
StartAudioContext(Tone.context, '#button').then(function(){
//started
})Copyright 2016 Yotam Mann