Re: [webkit-dev] Mac WK1 EWS bots having issues

2014-08-15 Thread Mark Rowe
> On Aug 15, 2014, at 09:22, Mark Rowe wrote: > >> >> On Aug 15, 2014, at 02:10, Osztrogonác Csaba > > wrote: >> >> Hi, >> >> it seems the Apple Mac WK1 EWS bots have problems: >> http://webkit-queues.appspot.com/queue-status/mac-ews >>

Re: [webkit-dev] Mac WK1 EWS bots having issues

2014-08-15 Thread Mark Rowe
> On Aug 15, 2014, at 02:10, Osztrogonác Csaba wrote: > > Hi, > > it seems the Apple Mac WK1 EWS bots have problems: > http://webkit-queues.appspot.com/queue-status/mac-ews > > Last Pass: 11 hours, 57 minutes ago by webkit-ews-01 > Unable to pass tests without patch (tree is red?) > > Regress

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 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

Re: [webkit-dev] WebAudio time domain sample data range?

2014-08-15 Thread Info
range seems indeed to be -1 to 1 (see RealtimeAnalyser::getByteTimeDomainData) Zitat von Info : What is the range of the input sample data that the webaudio implementation is dealing with (e.g. in /WebCore/Modules/webaudio/RealtimeAnalyser.cpp)? Is it float values between -1 and 1, or is t

[webkit-dev] Mac WK1 EWS bots having issues

2014-08-15 Thread Osztrogonác Csaba
Hi, it seems the Apple Mac WK1 EWS bots have problems: http://webkit-queues.appspot.com/queue-status/mac-ews Last Pass: 11 hours, 57 minutes ago by webkit-ews-01 Unable to pass tests without patch (tree is red?) Regressions: Unexpected text-only failures (30) compositing/plugins/composited-pl

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 : In order to understand the idiotic differences between the data ranges of the AnalyzerNode's getFloatFrequencyData() and getByteFrequencyData() APIs I fi