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

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

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:52 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/134/24244413@github.com>
> [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:
Received on Wednesday, 11 September 2013 14:35:55 UTC

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