W3C home > Mailing lists > Public > public-xg-audio@w3.org > June 2010

Re: Web Audio API Proposal

From: Maciej Stachowiak <mjs@apple.com>
Date: Tue, 15 Jun 2010 15:36:00 -0700
Cc: Chris Marrin <cmarrin@apple.com>, public-xg-audio@w3.org
Message-id: <5C10D99E-5744-4DE9-9BF6-000F2FA0C11B@apple.com>
To: robert@ocallahan.org

On Jun 15, 2010, at 3:29 PM, Robert O'Callahan wrote:

> Second, there are some implementations of JavaScript that will not be able to keep up with the processing of 48Khz stereo audio. These implementations will have to reduce the sample rate,which will make the FFT calculations less accurate. And even if an implementation is able to keep up with the data rate, it will leave very little for any other JavaScript to run at any sort of reasonable frame rate.
> So these must be platforms where "native" FFTs are much faster than any possible JS implementation. What accounts for that performance difference?

On many platforms, "native" FFTs are much faster than any possible C implementation, let alone JS.

Received on Tuesday, 15 June 2010 22:36:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:54:30 UTC