On Thu, Aug 28, 2014 at 4:17 AM, Chris Wilson <cwilso@google.com> wrote: > We're looking in to this more, but in short - don't create extra > AudioContexts unless there's some really, really important reason for > needing them. In general, use one per app. (We're working to make that > easier, with the suspend/resume/release proposal.) > Can't you just fix this in Chrome instead of asking Web devs to work around it? Firefox doesn't have this problem; multiple AudioContexts can share a single audio processing thread. Rob -- oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo owohooo osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o oioso oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo owohooo osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro ooofo otohoeo ofoioroeo ooofo ohoeololo.
Received on Thursday, 28 August 2014 02:13:38 UTC