update examples to reflect new Audio Autoplay Policy

[TomPeak]

Hello,

I use p5.sound on Chrome

please have a look: https://developers.google.com/web/updates/2017/09/autoplay-policy-changes#webaudio

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

There are some 2018 chances!

Tom

[lmccart]

I think the todo here is to add a note into the documentation and update any examples that autoplay to instead require user interaction (mousePressed etc).

[lmccart]

note that the documentation for sound examples is done here: https://github.com/processing/p5.js-sound

[limzykenneth]

For now this behaviour has been at least temporarily suspended, furthermore what Chrome is doing isn't standard compliant. How Chrome will or will not change their approach to this is still to be seen.

[lmccart]

this would mean updating files p5.dom.js and maybe also p5.Element.js. there are probably updates needed for the p5.sound library as well, but those live in a separate repo

[micuat]

I've encountered this problem with latest chrome when playing videos. Muted video can be autoplayed but video.volume(0) is not enough - only video.elt.muted = true works

[tigoe]

It's not just audio playback, I'm getting the same error when I try to use AudioIn and fft to do tone detection.

See https://github.com/tigoe/p5js_examples/tree/master/toneDetect for an example that fails reliably.

[dhowe]

Seems to me we either need to fix the fatal bugs (eg https://github.com/processing/p5.js-sound/issues/88) in p5.sound or give up on it and instruct folks to use something like Tone.js. If the latter, then we don't need to worry too much about this... (its quite frustrating for students who are instructed to use the sound lib, to then have it crash their sketches whenever they let them run for a while)