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

[Bug 17398] (AudioNodeAsAudioParam): AudioNode as input to AudioParam underdefined

From: <bugzilla@jessica.w3.org>
Date: Thu, 16 Aug 2012 23:33:22 +0000
Message-Id: <E1T29Z4-00087K-Do@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17398

--- Comment #5 from Chris Rogers <crogers@google.com> 2012-08-16 23:33:22 UTC ---
(In reply to comment #4)
> 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

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 16 August 2012 23:33:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 16 August 2012 23:33:26 GMT