W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Audio-ISSUE-41 (AudioNodeAsAudioParam): AudioNode as input to AudioParam underdefined [Web Audio API]

From: Audio Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 15 May 2012 14:40:13 +0000
Message-Id: <E1SUIv7-00023G-9G@tibor.w3.org>
To: public-audio@w3.org
Audio-ISSUE-41 (AudioNodeAsAudioParam): AudioNode as input to AudioParam underdefined [Web Audio API]

http://www.w3.org/2011/audio/track/issues/41

Raised by: Philip J├Ągenstedt
On product: Web Audio API

The output of an AudioNode can be connected with to an AudioParam value using AudioNode.connect(). Does that override scheduled value changes, or is the whole AudioParam interface "dead" in that case? In other words, which value takes priority, or are the mixed? (Similar to issue with multiple ramps.)

What happens if the input has multiple channels, which channel is used or is there implicit mixing?

Does AudioParam.unit affect how the input signal is mapped to a value?
Received on Tuesday, 15 May 2012 14:40:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 May 2012 14:40:19 GMT