[Webkit-unassigned] [Bug 190552] UI / DOM blocks audio thread, causing crackles

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=190552

--- Comment #2 from Jer Noble <jer.noble at apple.com> ---
(In reply to ae from comment #0)
> We're developing a WebAudio-based DAW running in a WKWebView. This works
> amazingly well and we're thrilled how far the Web Audio API has come.
> 
> However, when the engine is under high load (roundabout 500 nodes for the
> entire loaded project), interacting with the DOM (scrolling, adding /
> removing elements, etc.) in any way causes severe buffer underruns, even at
> 1024 frames buffer size (set by starting another app that sets that buffer
> size and records in the background).
> 
> Shouldn't the audio thread run with high priority and not be blocked by the
> UI / DOM thread?

Can you provide sample code? Unless you're using javascript-based nodes, WebAudio should be entirely off the main-thread.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20181017/b03e51bc/attachment.html>