What I proposed wasn't quite as good as AudioWorklet. But we probably could have made it so, if there had been interest.
-
-
Replying to @rocallahan @slightlylate and
What I proposed/implemented was certainly a lot better for scripted sample processing than what Web devs have had in the five years since.
2 replies 1 retweet 2 likes -
Lazy Mozilla should have done more to magically overcome the mix of "audio professionals agree" and "already shipped in WebKit". Bad us! /s
1 reply 0 retweets 1 like -
I don't think Alex was saying or thinking that. Anyway I'll assume he wasn't :-).
1 reply 0 retweets 1 like -
There were...spirited...debates about ScriptAudioNode within the Chrome team back then. It was clearly not fit for purpose.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @rocallahan and
I similarly got a lot of "trust us, we're audio professionals" from some quarters (and I very much am not).
1 reply 0 retweets 2 likes -
Replying to @slightlylate @rocallahan and
So I guess what I'm saying is that I'm sad it has taken us this long, but long live Audio Worklet?
1 reply 0 retweets 0 likes -
That's fair.
1 reply 0 retweets 0 likes -
Again, apologies for confusing your proposal with Audio Data API.
1 reply 0 retweets 1 like -
Sure, no problem.
2 replies 0 retweets 0 likes
One of the interesting things about how things have turned out is that the pro-layering camp (Extensible Web) usually wins in the long run.
-
-
Replying to @slightlylate @rocallahan and
The anti-JS "they'll just screw it up" ethos tends to lose because the bespoke thing can't predict enough use-cases.
0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.