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

[web-audio-api] (setTargetValueAtTime): AudioParam.setTargetValueAtTime is misleading and underdefined (#152)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:38 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/152@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17334](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17334) Tue, 05 Jun 2012 11:25:34 GMT
> Reported by Philip J├Ągenstedt
> Assigned to 

Audio-ISSUE-38 (setTargetValueAtTime): AudioParam.setTargetValueAtTime is misleading and underdefined [Web Audio API]

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

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

The naming of this function is misleading, since it does not in fact set the target value at the given time.

timeConstant is underdefined, what is the exponent? A "first-order filter (exponential)" is mentioned, but not clarified further.

Finally, it is not well defined what the difference to exponentialRampToValueAtTime is, but we suspect that setTargetValueAtTime is something like v=1-e-kt. The equations involving the 3 parameters should be included in the spec, normatively.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/152
Received on Wednesday, 11 September 2013 14:29:03 UTC

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