The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu

[swethamanur]

Hello,
Thanks for the code!
I am getting the following issue:
The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu

Could you please help me resolve?
Thanks

[DavidLazic]

@swethamanur

If you have set the autoplay option, it would fail these days on both desktop / mobile because of new web security rules. If I remember correctly, autoplaying video / audio content was allowed only in muted state.

[maxi032]

Hi. Can you please give more details into how to solve this?

[LazicDavid]

@maxi032

I'm guessing you're having the same problem on Chrome.
As the browser warning links to Google WebAudio, it's explained there that the Chrome WebAudio API doesn't support autoplay anymore.

You need to change the source code:

• Try creating the Visualiser instance on a user trigger event (e.g. click)
• Create custom volume control and set the decoded audio to a muted state initially (not sure if this will work).

So, yeah, I don't see a simple workaround.

[xewl]

To elaborate on this, @LazicDavid is correct and gives 2 valid options (well, at least 1, haven't tested the muted state).
Another option I've had success with is to check for an ?autoplay GET-parameter (decodeURIComponent), and to only set the audio stream when all scripts are loaded, based on that parameters' existence, only then starting the playback. [Use case was an online radio station]
(thought I'd share)

[ghost]

oh
firefox is working