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

Re: noteOn/noteOff and node lifetimes ...

From: lonce wyse <lonce.wyse@zwhome.org>
Date: Sun, 05 Aug 2012 12:41:47 +0800
Message-ID: <501DF98B.1050908@zwhome.org>
To: public-audio@w3.org

Hello,

 From where I sit, the problem is a usage issue:

> Oscillator and AudioBufferSourceNode
> objects can only be used once through noteOn/noteOff

because it seems inconsistent with the way other nodes can be used by 
creating a graph architecture, and "using them more than once" if you 
keep a reference to them around.

- lonce



On 5/8/2012 11:00 AM, Chris Rogers wrote:
>
>
> On Sat, Aug 4, 2012 at 7:49 PM, Srikumar Karaikudi Subramanian 
> <srikumarks@gmail.com <mailto:srikumarks@gmail.com>> wrote:
>
>     Hi all,
>
>     It appears that the Oscillator node's setup code for the
>     "basic waveforms" is needlessly run for every node ("voice")
>     instantiated. To avoid repeating the waveform setup code,
>     can we perhaps delegate the task of creating the basic
>     waveforms to the AudioContext object instead of the Oscillator
>     node? i.e. AudioContext.createWaveTable(type) can be
>     overloaded to return a wave table of the requested basic
>     waveform which can then be assigned to any number of
>     oscillator nodes.
>
>     Thoughts?
>
>
> Hi Kumar, I see you must have been poking around in the WebKit source 
> code to see this :)
> You've indeed found an inefficiency in the implementation, and might 
> consider filing a WebKit bug about this.  But, it's an implementation 
> detail and can be optimized there, without needing to modify the API.
>
> Cheers,
> Chris
Received on Sunday, 5 August 2012 04:43:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 5 August 2012 04:43:14 GMT