Closed stared closed 3 years ago
The "audio not starting" part of the issue can be fixed, but the warning will still be there. It will always appear at least a few times, as this is simply what chrome does on audio context creation. Tone creates it immediately on import and deferring the import isn't worth it. Also the only way to check if the browser requires the event is to create the context and see if it's already running. So the warning is inevitable.
When opening the main page, there is a warning (or actually: MANY warnings).
AFAIR Tone.js can be initialized only after user input.