Chrome 66 - The AudioContext was not allowed to start about sound HOT 10 OPEN

chrome://flags/
does have an "Autoplay policy" flag actually, so far it works. :)

from sound.

Thanks for the compliments.

I don’t think you can avoid this. We are heading to a world where all audio and video media requires an interaction. I’m not a huge fan either. You can design around it by creating a start button?

from sound.

It's a good idea, but one of the target devices (arcade box) will only have button controls connected to it (directional joystick, 5 action buttons), currently a keypress is not resuming the audio context. :(

I guess I can build with an older version of Chromium for now until the Chrome devs implement some none pointer-device way or resuming audio context...

from sound.

I wonder if there is there a flag in Chrome to prevent this behavior?

from sound.

Follow-up article: https://www.bleepingcomputer.com/news/google/google-fixes-issue-that-broke-millions-of-web-based-games-in-chrome/

Looks like they temporarily reverting the change until more developers can integrated interaction-to-play audio. I might add a note about this in the readme because it's an important design consideration.

from sound.

Sorry to bump an old post--

I added a "start" button that then plays the main menu state and starts the audio. Yet, I still get this warning:

The Web Audio autoplay policy will be re-enabled in Chrome 70 (October 2018). Please check that your website is compatible with it. https://goo.gl/7K7WLu

Is that warning something that always pops up? OR is it telling me my current implementation simply doesn't work correctly? Thanks!

from sound.

How do we resume the audio context after user interaction?

from sound.

Based on this setter @OptimusPi I believe you should be able to set paused = false, ala

PIXI.sound.context.paused = false;

from sound.

maybe it could be useful for someone, it took me a while sorting out those annoying warnings.

You can load dynamically 'pixi-sound' after a user click/swipe and store it in a lazy loader var.

if (!this.pixiSound) {
  this.pixiSound = await import('pixi-sound')
}

then, in order to use it:

  this.pixiSound.default

from sound.

Building off the previous comment, this work well for me:

document.addEventListener('click', async () => {
  globalThis.PIXI.sound = (await import('pixi-sound')).default;
}, { once: true });

from sound.