- From: Ehsan Akhgari <ehsan.akhgari@gmail.com>
- Date: Mon, 3 Jun 2013 09:15:57 -0400
- To: Frederick Umminger <frederick.umminger@gmail.com>
- Cc: "public-audio@w3.org" <public-audio@w3.org>
Received on Monday, 3 June 2013 13:17:10 UTC
Currently you should be able to use multiple AudioContexts if you need multiple distinct listeners, but then you would have to mirror the same graph structure for both. -- Ehsan <http://ehsanakhgari.org/> On Sat, May 18, 2013 at 3:04 AM, Frederick Umminger < frederick.umminger@gmail.com> wrote: > Hi, > > A long time ago it was proposed to basically move the AudioListener > attribute from AudioContext to AudioPannerNode in order to allow multiple > listeners. Whatever happened to this suggestion? > > Actually, even having the AudioListener as an attribute of the > AudioPannerNode is not quite correct, since that would require duplicating > AudioPannerNodes N times for N AudioListeners in the commonest case. > > Here are two use cases for multiple listeners > - sounds picked up from virtual microphones (e.g. spy microphones in a > game) > - merging sounds heard by all players in a split-screen game > > Is there some other way to handle multiple listeners in the current API? > > Sincerely, > Frederick > > >
Received on Monday, 3 June 2013 13:17:10 UTC