Fixed in r172816.
Dean
> On 15 Aug 2014, at 1:56 am, Info 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 :
>
>> In order to understand the idiotic differences between the data ranges of
Please file a bug at bugs.webkit.org.
Simon
On Aug 15, 2014, at 1:56 AM, Info 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 :
>
>> In order to understand the idiotic differences between
This seems to be a bug... that has been fixed in Chromium: see
chromium\src\third_party\WebKit\Source\modules\webaudio
Zitat von Info :
In order to understand the idiotic differences between the data
ranges of the AnalyzerNode's getFloatFrequencyData() and
getByteFrequencyData() APIs I fi
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/RealtimeAnal
4 matches
Mail list logo