W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

Re: Web Audio API sequencer capabilities

From: Joseph Berkovitz <joe@noteflight.com>
Date: Tue, 9 Oct 2012 12:56:46 -0400
Cc: Joseph Berkovitz <joe@noteflight.com>, Srikumar Karaikudi Subramanian <srikumarks@gmail.com>, Jussi Kalliokoski <jussi.kalliokoski@gmail.com>, "public-audio@w3.org Group" <public-audio@w3.org>
Message-Id: <2743F348-CB3A-4440-8BDE-5BA2B0431795@noteflight.com>
To: Chris Rogers <crogers@google.com>

On Oct 8, 2012, at 3:33 PM, Chris Rogers <crogers@google.com> wrote:

> If we extend the API in this direction in the future, rather than restore gain to ABSN, I would rather see a new type of node with an AudioParam driving its constant value. Such a node's only function is to emit a parameter-driven value.  In essence it's no more than a Node wrapping an AudioParam -- in fact, it could be named AudioParamSourceNode, by analogy with AudioBufferSourceNode.  Such a node can serve as both a unity source, a non-unity source, an envelope, or whatever.
> But this is so easy to create already.  I understand that it might save two or three lines of JS code, but that doesn't seem worth the effort to specify a whole new node.

It's OK, this is not something I care about much at all; happy to write the extra few lines of code.  Hence my conditional statement "If we extend the API in this direction in the future…" 

Received on Tuesday, 9 October 2012 16:57:15 UTC

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