Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Safari OfflineAudioContext NotSupportedError (also in examples)
See original GitHub issueIn Safari on a desktop Mac I’m getting a NotSupportedError: The operation is not supported.
It is also happening in the offline example: https://tonejs.github.io/examples/offline.html
Is this a bug or is there a way to work around this? Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
web audio api - OfflineAudioContext and FFT in Safari
All works fine in Chrome, Firefox and Opera but in Safari I get a very dodgy behaviour. The waveform should be composed by...
Read more >OfflineAudioContext() - Web APIs - MDN Web Docs - Mozilla
An integer specifying the size of the buffer to create for the audio context, in sample-frames, where one sample-frame is a unit that...
Read more >standardized-audio-context - npm
A cross-browser wrapper for the Web Audio API which aims to closely follow the standard.. Latest version: 25.3.36, last published: 22 days ...
Read more >Web Audio API - W3C
The OfflineAudioContext can be constructed with the same arguments as AudioContext.createBuffer. A NotSupportedError exception MUST be ...
Read more >AudioContext() - Web APIs
NotSupportedError : The specified sampleRate isn't supported by the context. ... This example creates a new AudioContext for interactive audio (optimizing ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I don’t think there is anything that i can do about this, seems more like a Safari + Web Audio issue than anything Tone.js specific. Going to close, but open to ideas if anyone comes across a solution or a way to reproduce the issue more consistently.
Does the same issue happen if you try and open a vanilla Web Audio API (non-Tone.js) page in Safari under those circumstances?
Given how you reproduce the error, i don’t think there is much Tone.js could do about it. Seems like a Safari issue. But if we can pinpoint its cause, maybe there’s a sensible error that could be thrown instead of just NotSupportedError.
My only guess without being able to reproduce the issue is that i think all browsers have a hard limit on the number of simultaneous AudioContexts that can be open at once across the entire system, not just per-page. it’s possible that Google Meet was using one of those AudioContexts which tipped your page over the edge.