W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: Web Audio thoughts

From: <mage@opera.com>
Date: Tue, 12 Jun 2012 18:33:24 +0000
Message-ID: <20120612183324.66jajjlji1s0swc0@staff.opera.com>
To: Chris Rogers <crogers@google.com>
Cc: Ray Bellis <ray@bellis.me.uk>, public-audio@w3.org
Citerar Chris Rogers <crogers@google.com>:

> On Tue, Jun 12, 2012 at 9:21 AM, Ray Bellis <ray@bellis.me.uk> wrote:
>
>> 1.  AudioParam variables
>>
>> There's no way I can see to have an AudioParam property in a
>> JavascriptAudioNode and then have that node sample the parameter.  The
>> JS node is very useful, but without access to AudioParam features it's
>> kind of a second class citizen.
>>
>
> Yes, Jussi has brought this up before, and we agreed it could be useful.
> But for now at least, we're not adding this part in.  We could add this in
> the future...

Actually, I re-opened the issue [1] (apologies for my late arrival to  
the discussion), since it seems to be a fundamental feature of the  
API. As Ray says, JavascriptAudioNode is really a crippled second  
class citizen without proper support for AudioParam. Not sure if we're  
ready for another round of this discussion, but I really think that it  
would be a very valuable addition to the API.

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=17388

>>
>> I can't even implement a custom JS oscillator that has the same external
>> interface as the standard Oscillator without access to AudioParams.
>>

  /Marcus
Received on Tuesday, 12 June 2012 18:34:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 12 June 2012 18:34:45 GMT