3 ms·
I get that too on Firefox, I'm hoping to try out the web-worker idea suggested by meandave to fix it. At the moment it works much better on Chrome for some reas
by errozero 12y ago
I get that too on Firefox, I'm hoping to try out the web-worker idea suggested by meandave to fix it. At the moment it works much better on Chrome for some reason.
- padenot 12y ago(Firefox Web audio developer here) It's because, we've not optimised our implementation _at all_ (I'm exaggerating a bit but you get the idea). That said now that Firefox's implementation is in good shape in terms of spec compliance, we have started (very recently, one week or something) to work on performance.
- errozero 12y agoThat's good to hear. Just noticed your username and remembered you commented on a stack overflow thread of mine whilst I was developing this, about 24db filters: http://stackoverflow.com/questions/28502028/web-audio-api-24db-filter http://stackoverflow.com/questions/28502028/web-audio-api-24...