No, ALL audio drops samples now, because the mixer thread can't be realtime priority anymore, because it can run JS
-
-
Replying to @antumbral @slightlylate
There are lots of bug reports about it. My high-end machine can reproduce it with a simple HTML file that plays one sample in a loop.
1 reply 0 retweets 1 like -
Replying to @antumbral @slightlylate
I'm sure changes will be made to mitigate it, but the architecture-dev thread has some people saying it's okay to glitch.
1 reply 0 retweets 0 likes -
Replying to @antumbral
I think it's OK to glitch the app/site that's offending, but not all audio.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
Yeah. In this case no AudioWorkers are in use anywhere in the browser.
1 reply 0 retweets 1 like -
-
Replying to @slightlylate @cwilso
Maybe I misinterpreted the discussion thread and spec allows JS run on its own thread(s) like VST plugins? That would mitigate the damage.
2 replies 0 retweets 0 likes -
Replying to @antumbral @slightlylate2 replies 0 retweets 1 like
-
re: other tweet I assume part of the issue here is that too many threads means more buffering, higher latency?
1 reply 0 retweets 0 likes -
Replying to @antumbral @cwilso and
And many WebAudio use cases want low latency, so that limits your ability to use threading configurations that a DAW might use?
1 reply 0 retweets 0 likes
All audio cases want low latency = ) I think the question here was balance about letting JS run on any realtime thread vs. latency.
-
-
I'm guessing cost of changing thread priority dynamically (on context switch between native/js) is too high, or pri switch is delayed?
2 replies 0 retweets 0 likes -
Replying to @antumbral @slightlylate and
If the mixer dropped priority while running JS, that would be great. I know thread schedulers can dynamically adjust thread priority.
1 reply 0 retweets 0 likes - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.