This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21596 - Spec what happens if a AudioBufferSourceNode is connected to two distinct PannerNodes
Summary: Spec what happens if a AudioBufferSourceNode is connected to two distinct Pan...
Status: CLOSED WONTFIX
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: TBD
Assignee: Chris Rogers
QA Contact: public-audio
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-05 15:46 UTC by paul@paul.cx
Modified: 2014-10-28 17:17 UTC (History)
0 users

See Also:

Attachments

Description paul@paul.cx 2013-04-05 15:46:48 UTC 
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.
Comment 1 Olivier Thereaux 2014-10-28 17:14:50 UTC 
Web Audio API issues have been migrated to Github. 
See https://github.com/WebAudio/web-audio-api/issues
Comment 2 Olivier Thereaux 2014-10-28 17:17:49 UTC 
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.