On Mon, Oct 17, 2011 at 4:23 PM, Olli Pettay <Olli.Pettay@helsinki.fi>wrote: > On 10/14/2011 03:47 AM, Robert O'Callahan wrote: > > The big thing it doesn't have is a library of native effects like the >> Web Audio API has, although there is infrastructure for specifying named >> native effects and attaching effect parameters to streams. I would love >> to combine my proposal with the Web Audio effects. >> > > > As far as I see Web Audio doesn't actually specify the effects in any > way, I mean the algorithms, so having two implementations to do the > same thing would be more than lucky. That is not, IMO, something we > should expose to the web, at least not in the audio/media core API. > I'm a bit perplexed by this statement. The AudioNodes represent established audio building blocks used in audio engineering for decades. They have very mathematically precise algorithms. Audio engineering and computer music theory has a long tradition, and has been well studied. Chris
Received on Tuesday, 18 October 2011 00:48:13 UTC