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

Re: FFT & IFFT with the Web Audio API

From: Ehsan Akhgari <ehsan.akhgari@gmail.com>
Date: Thu, 20 Jun 2013 20:52:39 -0400
Message-ID: <CANTur_663m5YPhukMFQs_fTTgDrUsbWT_kpXqoeJp=Pqs+4_3g@mail.gmail.com>
To: Jens Nockert <jens@nockert.se>
Cc: "public-audio@w3.org" <public-audio@w3.org>
On Thu, Jun 20, 2013 at 6:56 PM, Jens Nockert <jens@nockert.se> wrote:

>
> On 19 Jun 2013, at 17:28, Ehsan Akhgari <ehsan.akhgari@gmail.com> wrote:
>
> > I don't think that the limitation to 32-bit floating point was a good
> design decision in Web Audio, because it basically ignores all of the
> devices without FPUs or other mobile devices on which floating point
> computations are slow.  It could be that some browser engines don't care
> about such devices, but Gecko does.
>
> We cannot really change that Javascript only supports floating-point right
> now.
>
> While I agree that maybe you should make a DSP API extendable to
> fixed-point types in the future, the current state of Javascript kind of
> prevents us from using non-floats for just about anything.
>

Well, in Javascript all numbers are 64-bit doubles, so JS as it is today is
not quite amenable to 32-bit floats any more than it is to integers.
However modern JITs that are available in all web browsers these days are
smart enough to special case integers.

--
Ehsan
<http://ehsanakhgari.org/>
Received on Friday, 21 June 2013 00:53:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:18 UTC