- Chrome shipped AudioWorklet in M64 via Origin Trial.
- FireFox publicly supports the specification and started working on it.
Any plans on implementing audioworklet?
AudioWorket has a big improvement on voice quality when applications based on webaudio
"AudioWorket has a big improvement on voice quality when applications based on webaudio, especially when the main thread is busy."
*** Bug 185063 has been marked as a duplicate of this bug. ***
Would love to see this implemented. ScriptProcessor introduces too many audio glitches to be used in a professional capacity.
also v keen to see this implemented in webkit. v useful / powerful tool for webdev and sound design more generally. blink's had this working for a couple of years now - would be *awesome* to have it working on iOS.
Just chiming in to say that this would be a very welcome feature in Safari. The team at Mozilla have recently shipped a very solid implementation of AudioWorklet (https://hacks.mozilla.org/2020/05/high-performance-web-audio-with-audioworklet-in-firefox/), making Safari the one major browser that still requires the use of ScriptProcessor for custom audio processing. Given the excellent hardware on Mac and iOS devices, and the very performant visual rendering in Safari, it would be really wonderful for developers working on sound & music projects to be able to run custom audio processing DSP off the main thread with low-latency. Projects like https://learningsynths.ableton.com/ would benefit greatly.
I'm adding to all the voices... My team develops WebAudio plugins and the last 70 we wrote use WebAudio worklets. We teamed with some of the DAW vendors, AW is a must have feature.
On behalf of my team at https://www.ampedstudio.com, and as a member of the broader WebAudio community, I too want to express the importance of Safari supporting AudioWorklet. The ecosystem of mature projects built around this feature is quite large but was long held back by lack of cross-browser support. As others have mentioned this is finally changing with recently added FF support and Edge's switch to Chromium, but Safari is still a big gap
It would be good to see this issue starting to be resolved now, or to be provided with the reason(s) why WebKit/Safari still does not support AudioWorklet.
ScriptProcessorNode is deprecated so it would be risky to use as a fallback even if the main thread could comfortably deal with it. The only option we really have right now is to not support Safari when AudioWorklet is required in an audio-centric web application.
Support is fine in other browsers (Chrome, Edge, Firefox, Opera):
Hello, I would like to add my support to the requests that have been made here. Implementing AudioWorklet is a big step forward for web audio. However, without support in Safari on macOS and iOS, applications relying on the low-level audio processing AudioWorklet enables (in conjunction with wasm, for example) are not feasible as widely accessible web experiences. The continued lack of support for AudioWorklet in Safari discourages creative/innovative use of the web platform.