Re: [web-audio-api] (audioparam): AudioParam constructor (#134)

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17388#1) by Olivier Thereaux on W3C Bugzilla. Thu, 07 Jun 2012 14:31:45 GMT

Comment from Marcus Geelnard, 4 Jun 2012, 08:07:19
«
First of all, sorry for being late with input to this. I hope I did the right thing here by re-opening the issue (?).

Adding to the previous discussions, I strongly feel that this is an important feature of the API.

Without the ability to have AudioParams on JavaScriptAudioNodes, it would not be possible to re-implement the native nodes for instance, e.g. for testing and reference implementations. It also makes it far more difficult to do drop-in replacements in an existing graph (e.g. if a developer wanted to make a custom filter node to replace a BiQuadFilterNode in an existing graph).

Generally speaking, it seems logical that the JavaScriptAudioNode is the most generic node with which you can implement "everything". Hence, support for AudioParam seems like a fundamental requirement.
»

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/134#issuecomment-24244413