Open Moxinilian opened 3 years ago
Thanks for the issue!
cc @dpeckett as they did the lion's share of the work in landing the webaudio host - any advice or thoughts on this would be greatly appreciated!
@Moxinilian I did notice the timeouts as well - my assumption was that these worked by "scheduling" the function to get called after the amount of time has passed, freeing the process to do work in the meantime, but I'm certainly not familiar enough with WASM or the webaudio backend to be sure. Either way, I think you're right that it would be nice to document this behaviour too. A PR adding a note about the WebAudio behaviour (once we get to the bottom of it) would be very welcome.
The main page of the documentation states
However, this is difficult to understand in the context of wasm. In fact, I believe in the WebAudio host it is not the case: the processing seems to happen in a timeout event which as far as I know is not a dedicated thread. Perhaps adding some clarification about wasm would help?