- From: Kaustubh Joshi <kdj.tikka@gmail.com>
- Date: Mon, 17 Jun 2013 20:24:06 +0530
- To: Michael Weitnauer <weitnauer@irt.de>
- Cc: public-audio@w3.org
- Message-ID: <CAPHiY=coN53sis_pQBmrRq8BJ-88ba5Fy38HZKxrvq6O-SxisA@mail.gmail.com>
Hi Michael, As per my understanding, FFT API is kept kind of portable for different library like FFMPEG or platform based instruction usage (MAC,Intel,AM-Neon). FFT-FFMPEG usage would be quite good performance with best compiler options. br, kaustubh On Mon, Jun 17, 2013 at 7:29 PM, Michael Weitnauer <weitnauer@irt.de> wrote: > Hi all, > > I wonder why you guys didn't implement a "real" or proper FFT and IFFT > method for the Web Audio API. I wanted to implement some signal processing > stuff with the API as I recognized the lack of getting complex values > buffers. From my understanding offering a real FFT and IFFT method should > be quite simple as you definitively conduct a FFT somewhere in the > background. > > From my point of view, it would be a great benefit for the API and future > audio applications in browsers if there would be the (native) possibility > to apply a FFT and IFFT as these are the main tools for signal processing > stuff as you all know. I'm quite sure you agree with me in this > point. Hence, I wonder if there is a chance to include these features in > the API. Probably, you had a special reason for not including a real > general-prupose FFT and IFFT method? > > Best wishes, > Michael > > > > --------------------------------------------------------- > Michael Weitnauer > Production Systems Audio > > Institut fuer Rundfunktechnik GmbH (IRT) > R&D Institute of ARD, ZDF, DRadio, ORF and SRG/SSR > Floriansmuehlstr. 60, D-80939 Muenchen, Germany > > Email: weitnauer@irt.de > Web: http://www.irt.de > Phone: +49 89 32399-387 > > > Managing director: Dr. Klaus Illgner-Fehns > Registration court: Munich Commercial, Register No. B 5191 > >
Received on Monday, 17 June 2013 14:54:36 UTC