Caniuse: AudioWorklet

Created on 9 Apr 2018 · 8Comments · Source: Fyrd/caniuse

WebAudio API has been updated to add AudioWorklet [1], to replace (deprecated) ScriptProcessor API.
This will allow to run custom JS code directly within the audio thread, instead of the main thread, preventing glitch and other issues which can arise when audio processing isn't real time.
Chrome shipped this feature [2].

canise already have a page for WebAudio API, but since this sounds like a major feature to me, I believe it would be nice to have a dedicated page for AudioWorklet.
Or do you think this having a note on the current WebAudio API page will be enough?

Support data suggestion

Source

ArnaudBienner

👍15

Most helpful comment

Any news on this? I'd like to include a caniuse link from my Worklet editor for users to learn which browser supports AW when theirs don't.

cristiano-belloni on 7 Sep 2018

👍3

All 8 comments

I'm fine to do a pull request for this, but wanted to know first if it was worth it.

ArnaudBienner on 9 Apr 2018

Regardless of implementation (a note on the current WebAudio page or a separate page), it would be great if I could type 'AudioWorklet' on caniuse and see this information, wherever it happens to live.

nchase on 3 May 2018

This is pretty major in my opinion. Web Audio has been waiting for Audio Worklet to finally be ready for years now (I've been following Web Audio developments since ~2011). ScriptProcessorNode was officially deprecated in 2014 without this replacement actually being ready until recently.

BillyWM on 5 Jul 2018

👍3

Any news on this? I'd like to include a caniuse link from my Worklet editor for users to learn which browser supports AW when theirs don't.

cristiano-belloni on 7 Sep 2018

👍3

I have just searched caniuse.com and was expecting a search for audio worklet to return supported browser versions, but no results were returned. It has been available in Chrome since version 66.

This is one of those features that should, IMHO, have its own table because Web Audio support doesn't necessarily mean Audio Worklet support. The same is true for WebGL and WebGL2, but those have separate compatibility tables.