This seems to be a bug... that has been fixed in Chromium: see
chromium\src\third_party\WebKit\Source\modules\webaudio
Zitat von Info <[email protected]>:
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:
https://github.com/WebKit/webkit/blob/master/Source/WebCore/Modules/webaudio/RealtimeAnalyser.cpp
What surprises me there is the:
const double magnitudeScale = 1.0 / DefaultFFTSize;
which is used to normalize the FFT results (see
RealtimeAnalyser::doFFTAnalysis()).
Should the correct scaling factor not rather be: 2/actualFftSize?
_______________________________________________
webkit-dev mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________
webkit-dev mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-dev
