beta
cables is under heavy development.
There might be one or another bug, please let us know about it!
WebAudioContextRunner
Ops.Deprecated.WebAudio.WebAudioContextRunner
Resumes the Web Audio context (unmute on Chrome / iOS)

summary (oneliner)

Some browser have a strict autoplay policy. In Google Chrome and mobile iOS audio cannot be played unless the playback was initiated by a user gesture (click / tap). To free the audio context from the so called suspended state, a user interaction is needed which triggers the ResumeAudioContext op.
It has two modes – in the default one Show Overlay: true it will show an overlay over the cables canvas with a play button when the audio context is suspended.
When Show Overlay is set to false you have to manually take care of the user interaction (e.g. by adding a button yourself), registering a click / touch even listener and finally triggering Resume on this op.

doc

issues

youtube id

collections

related ops

Inputs

Show Overlay (boolean /Number)

Shows a button to unblock the audio context when set to true (only when it is blocked)


Resume (Trigger)

If Show Overlay is set to true you don’t need to connect this. It is only needed when set to false and needs to be manually triggered after a user interaction.


Outputs

Current State (string Number)

The current Web Audio state, updated whenever it changes (via event listener), either running or suspended


Caught a mistake or want to contribute to the documentation?

Edit Documentationcancel save

Credits


Changelog


Ops.WebAudio.WebAudioContextRunner renamed to Ops.Deprecated.WebAudio.WebAudioContextRunner
2021-09-21 - pandur

Examples using WebAudioContextRunner

Public Patches using WebAudioContextRunner