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:53 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/131/24244478@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17335#13) by redman on W3C Bugzilla. Tue, 11 Dec 2012 19:38:41 GMT

Is there anything against the idea of having separate interpolator objects?
I start to realize that a lot of the time you want to make a choice *if* and *how* you want to interpolate. So why not have interpolation as a separate module that you can plug in front of an AudioParam.
Or is this a crazy idea? :)

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

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