W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[web-audio-api] (AudioNodeAsAudioParam): AudioNode as input to AudioParam underdefined (#159)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:43 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/159@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17398](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17398) Tue, 05 Jun 2012 12:18:45 GMT
> Reported by Michael[tm] Smith
> Assigned to 

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


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?

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:31:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC