Original my message has been changed. 
Sorry.

Sent from Mobiledesk


---Original Message---
Sender : KeonHo Kim
Date : 2014/03/01 07:08 (GMT+09:00)
Subject : Re: Re: Serial connection between multiple pannerNodes recursively
Webkit/blink implementation is refered one pannerNode that is connected at final for doppler rate. Distance, sound cone, azimuth and elevation
are affected all connected panner. If there is no connection changing, an audiobuffersource refers only one panner and final for dopplerRate.

@Ray, could you check it togather, am I correct?
Actally, I had checked implementation.

@choihongchan
Thanks for additional description.
That was exactly I intended to ask.
The "recursively" can be ignored.

-Khno

Sent from Mobiledesk


---Original Message---
Sender : Chris Wilson/cwilso@google.com
Date : 2014/03/01 04:06 (GMT+09:00)
Subject : Re: Serial connection between multiple pannerNodes recursively

Hmm.  Though I can see how this would work with classic pan positions, when using the HRTF rather than equal-power, it seems like this would kinda fall apart.

IIRC, the issue in blink is related to our Doppler implementation.`



On Fri, Feb 28, 2014 at 9:46 AM, Hongchan Choi <choihongchan@gmail.com> wrote:
Hi Ray!

The serial connection of two different panner nodes is not that unusual. Actually, it is quite common in the music production software. For example, you can create a mix group with multiple audio streams (which has individual pan position) and you can control the stereo position of the whole mix group with the last panner node. So being able to create a serial connection with multiple panners should be possible or even essential, I guess.

However, I am not sure what the 'recursive serial connection' means in the question, and also the meaning of the second example is unclear to me. Is this about implementing Doppler effect by creating a loop between multiple panner nodes?

-Hongchan




On Fri, Feb 28, 2014 at 9:12 AM, Raymond Toy <rtoy@google.com> wrote:
You've been reading the blink/webkit code for panners. :-)

I do not know the reason, but it seems Chris Rogers only expected to have each source connected to at most one panner.  What would it mean to have a source connected to two different panners serially?


On Thu, Feb 27, 2014 at 4:27 AM, KeonHo Kim <keonho07.kim@samsung.com> wrote:

Dear All,

 

Here is an question about connection between multiple pannerNodes.

 

Example,

Source1 -> Panner1 -> 

                           Panner3 -> Destination

Source2 -> Panner2 ->

 

In this case, generated buffers from Source1 refer values such as dopplerShift, distanceConeGain, azimuth and elevation from Panner1 and Panner3.

In the next connection, generated buffers from Source2 refer values from Panner2 and Panner3.

 

If there is recursively serial connection between multiple panner nodes to audiobuffersourcenode, which panners should affect the pitch of audioBufferSource for dopper shift.

 

In example, Source1 ( Panner1 or Panner3, both ? )

Destination = Panner3 ( Panner1 ( Source1 ) ) ) ?

Destination = Panner1 ( Source1 ) ?

Destination = Panner3 ( Source1 ) ?

 

On process of each AudioNode will generate buffers for their purpose.

Is there anyone can guide clearly this case about all values how to work?





--
Hongchan Choi

PhD Candidate, Research Assistant
Center for Computer Research in Music and Acoustics (CCRMA)
Stanford University