Looks like the existing WebAudio issue https://github.com/WebAudio/web-audio-api/issues/1471 <https://github.com/WebAudio/web-audio-api/issues/1471> is where this should get resolved (for people who haven’t switched over there yet).
Best regards Nils Ohlmeier > On May 2, 2018, at 09:05, hongc...@chromium.org wrote: > > It's great to see the intent for the AudioWorklet, but also I can see the GC > observability is still being discussed here. > > Karl, can you open a new spec issue if you think this needs another look from > AudioWG and TAG? > > -Hongchan > > > On Wednesday, May 2, 2018 at 8:17:30 AM UTC-7, Boris Zbarsky wrote: >> On 5/2/18 5:21 AM, Karl Tomlinson wrote: >>> [[AudioNode Lifetime]] https://github.com/WebAudio/web-audio-api/issues/1471 >> >> I've read through that thread, but I'm still a little unclear on where >> thing stand. With the latest proposal, can there be observable >> situations where the output sound depends on GC timing? >> >> If so, that doesn't sound acceptable. It also sounds to me like Alex >> Russell in >> https://github.com/WebAudio/web-audio-api/issues/1471#issuecomment-362604396 >> didn't believe there was an observable sound difference possible. If >> one is possible, we should communicate this to him very clearly.... >> >> -Boris > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
