Spec what happens if a AudioBufferSourceNode is connected to two distinct PannerNodes

[olivierthereaux]

Originally reported on W3C Bugzilla ISSUE-21596 Fri, 05 Apr 2013 15:46:48 GMT
Reported by paul@paul.cx
Assigned to

Say we have the following setup:

Source1 ----> Panner1 ----> Destination
| |
`---> Panner2 --------'

Where:

• Source1 is an AudioBufferSourceNode ;
• Panner1 and Panner2 are two PannerNodes, with listener and source velocity set such as the doppler shift is different from 1.0 ;
• Destination is the context's destination node.

The spec seems to assume that an AudioBufferSourceNode can be connected to only one PannerNode.

[joeberkovitz]

@padenot I'm sorry, I can't find the assumption that you're referring to. Is there still a problem here?

[padenot]

A PannerNode can adjust the playbackRate of AudioBufferSourceNodes that are connected directly or indirectly (quoting the spec), to simulate a doppler effect. What is not specced is what happens when you have multiple PannerNode, having two different velocity values, downstream of a single AudioBufferSourceNode.

But we are talking about changing this AudioNode in a way that would make fixing this useless, so let's wait until we know what will happen to the PannerNode

[joeberkovitz]

OMG. I never read this section carefully. IMHO we must get rid of this doppler thing if that is how it's supposed to work (and I know Chris would like to).

[joeberkovitz]

#372 may render this moot.

[padenot]

I agree it's certainly not the most useful feature of the API.

[cwilso]

It's the hackiest part of the entire API as well. At a minimum with PannerNode, we should remove Doppler effects: remove dopplerFactor and speedOfSound from AudioListener, and remove setVelocity from PannerNode and AudioListener.

[cwilso]

Closing this, as it's obviated by #372 .