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

Re: [web-audio-api] (setValueCurveAtTime): AudioParam.setValueCurveAtTime (#131)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:54 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/131/24244438@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17335#8) by redman on W3C Bugzilla. Fri, 07 Dec 2012 14:29:30 GMT

(In reply to [comment #8](#issuecomment-24244432))
> redman, are you suggesting that other curves (setValueAtTime,
> linearRampToValueAtTime, exponentialRampToValueAtTime and setTargetAtTime)
> should be subject to filtering too? Not sure if you can construct a case
> where you get out-of-band frequencies using those, but I guess you can (e.g.
> an exponential ramp with a very short duration).

Certainly not! :)
No, just refering to curves.

As for the other other parameters, it would be handy to have a 'better than linear/ramp' interpolator that can be switched on or off.
But (AA)filtering would only be necessary when oversampling, as can be the case with curves.

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

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