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

Re: [web-audio-api] AudioParam - min/maxValue, intrinsic value, computedValue (#46)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:26 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/46/24244120@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=21545#2) by Chris Rogers on W3C Bugzilla. Tue, 16 Jul 2013 19:15:46 GMT

(In reply to [comment #2](#issuecomment-24244117))
> Following up on this bug, the prose for the intrinsic value is currently
> saying that when read, AudioParam.value should return the current instrinsic
> value based on the current time.  This is similar to what the computedValue
> attribute used to return, and there are some concerns about this (see
> <http://lists.w3.org/Archives/Public/public-audio/2012OctDec/0623.html> for
> example.)
> 
> Chris, are you planning to make AudioParam.value a simple value which can be
> get/set like any other attribute?

The .computedValue attribute was removed awhile ago as a publicly available attribute in the spec.  There is still a section talking about "computedValued", but only as an implementation detail to describe that this is the final internally computed value that will be used by the DSP algorithm.

I now see that I forgot to remove a couple of sentences relating to this - now fixed:
https://dvcs.w3.org/hg/audio/rev/4f8714b58ef1

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

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC