Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Thanks, this is very useful! Follow up questions, if you see them:

1. Does what you said include ScriptProcessorNodes?

2. Is this true of all browsers per specification, or true of a particular browser's implementation? My experience with web audio has been that in Chrome things work as you say, but in FF I could never find a webaudio library that played back without heavy clicking, so I supposed audio workers might help.

3. Given what you said, what will be different about Worklets? I scanned the links but I guess I don't follow the bigger picture.




1. No, it's the one thing that has to be on the main thread per spec.

2. It's true for all browsers. ScriptProcessor runs on the main thread and can be glitchier in Firefox (but depending on the use case it can be the opposite). See https://padenot.github.io/web-audio-perf/#scriptprocessornod... for more details.

3. Worklets are bits or javascript that run on the audio thread directly, where you're supposed to only implement the DSP bits, and only communicate with the main thread using message passing.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: