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

Re: AudioParam namespace in AudioWorkerNode

From: Chris Wilson <cwilso@google.com>
Date: Mon, 25 Aug 2014 14:25:03 -0700
Message-ID: <CAJK2wqVkYkPYjuHmahfXcEYaPrsEx=aX=Kz00n39kzoHj-qzRQ@mail.gmail.com>
To: Joseph Berkovitz <joe@noteflight.com>
Cc: "public-audio@w3.org" <public-audio@w3.org>
Sounds like an excellent idea that I should have considered.  I made this
change in the proposal hosted on cwilso.github.io/web-audio-api.


On Mon, Aug 25, 2014 at 2:16 PM, Joseph Berkovitz <joe@noteflight.com>
wrote:

> Chris,
>
> One further piece of feedback, breaking out into a separate thread here.
>
> To keep the parameter namespace clean, I think the dynamic AudioParams
> should be bound to properties of a separate “params” object hanging off of
> AudioProcessingEvent, rather than properties of the event itself.
>
> 1. This prevents any possible collision between parameter names and other
> event properties, of which there are many (and perhaps more in the future).
>
> 2. It also makes it much easier for application code to enumerate the
> AudioParams associated with a given event instance; no need to skip over
> the “builtin” properties of an Event as one iterates.
>
> So:
>
> interface AudioProcessingEvent : Event
>  {
>     readonly    attribute double      playbackTime;
>     readonly    attribute AudioBuffer inputBuffer;
>     readonly    attribute AudioBuffer outputBuffer;
>     readonly    attribute object params;        *// dynamic parameters
> hang off this object*
> };
>
> Thoughts?
>
> …Joe
>
Received on Monday, 25 August 2014 21:25:30 UTC

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