Re: [webkit-dev] FFT normalization in RealtimeAnalyser

2014-08-20 Thread Dean Jackson
Fixed in r172816. Dean On 15 Aug 2014, at 1:56 am, Info i...@wothke.ch wrote: This seems to be a bug... that has been fixed in Chromium: see chromium\src\third_party\WebKit\Source\modules\webaudio Zitat von Info i...@wothke.ch: In order to understand the idiotic differences between

Re: [webkit-dev] FFT normalization in RealtimeAnalyser

2014-08-15 Thread Info
This seems to be a bug... that has been fixed in Chromium: see chromium\src\third_party\WebKit\Source\modules\webaudio Zitat von Info i...@wothke.ch: In order to understand the idiotic differences between the data ranges of the AnalyzerNode's getFloatFrequencyData() and

Re: [webkit-dev] FFT normalization in RealtimeAnalyser

2014-08-15 Thread Simon Fraser
Please file a bug at bugs.webkit.org. Simon On Aug 15, 2014, at 1:56 AM, Info i...@wothke.ch wrote: This seems to be a bug... that has been fixed in Chromium: see chromium\src\third_party\WebKit\Source\modules\webaudio Zitat von Info i...@wothke.ch: In order to understand the idiotic

[webkit-dev] FFT normalization in RealtimeAnalyser

2014-08-14 Thread Info
In order to understand the idiotic differences between the data ranges of the AnalyzerNode's getFloatFrequencyData() and getByteFrequencyData() APIs I finally found myself analyzing the WebKit sources: