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

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

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:30:01 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/159/24244587@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17398#4) by Chris Rogers on W3C Bugzilla. Thu, 16 Aug 2012 23:33:22 GMT

(In reply to [comment #4](#issuecomment-24244579))
> I'm still a bit confused. The changes describe how the connect() method works.
> I think a better way to specify this is in the AudioParam section, with a
> complete description of how the final parameter value is calculated. This would
> include:
> 
> 1) The .value attribute
> 2) The automation values (scheduled changes)
> 3) The connected inputs
> 
> My current assumption would be something like:
> 
> [.value attribute] + [automation curve] + sum(mono(inputs))
> 
> Also, the specification needs to define what the default values of each
> contributing factor are. For instance if no events are scheduled or if no
> inputs are connected.
> 
> Also, what happens if cancelScheduledValues() is called with time = 0 or
> -Infinity? Will the automation curve return to its default value, keep its
> current value, or throw an exception?

Much more detail for how AudioParam values are calculated added here:
https://dvcs.w3.org/hg/audio/rev/41db9905149d

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/159#issuecomment-24244587
Received on Wednesday, 11 September 2013 14:37:08 UTC

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