- From: André Michelle <andre.michelle@audiotool.com>
- Date: Mon, 27 Mar 2017 21:57:20 +0200
- To: "public-audio-dev@w3.org" <public-audio-dev@w3.org>
Received on Monday, 27 March 2017 19:57:51 UTC
Hey! What is the current state of the AudioWorklet? It is very important for us to know when we can use it. The AudioWorklet would improve the experience of our application in many ways. The most obvious is that we expect way less glitches. We know that buffer-underruns can still happen but in very most cases the main-thread was using a little(!) bit more time than we can allow to maintain seamless playback with a reasonable latency. We already improved it a lot by not(!) using a ScriptProcessor. BufferSourceNodes can be scheduled seamlessly and offer more control and glitch-detection. The audio-rendering is already done inside a worker and sent to the main-thread. But this is where the bad glitches are happening. Small things like layout changes can have an immediate impact on the playback. We also have a version where we use another Browser-TAB to render and playback the audio. This solution works actually best (reduces glitches up to 75% allowing 60fps animations). But this is hardly a solution for long. Any pointers are welcome. ~ André Michelle http://www.audiotool.com
Received on Monday, 27 March 2017 19:57:51 UTC