Re: [web-audio-api testing] Best way of testing an AudioNode output

Thanks for your suggestions, Chris. It does make sense as a general
guideline for testing, as the reply given by Chris Lowis.
On Oct 28, 2013 2:09 AM, "Chris Wilson" <cwilso@google.com> wrote:

> AnalyserNode is probably a very bad way to get any kind of predictable
> testing results out of the API, since you'll likely have timing challenges
> if you're trying to use it to do waveform comparisons.  OfflineAudioContext
> is probably best, ScriptProcessor second.
>
>
> On Sat, Oct 26, 2013 at 1:40 PM, Amitay Dobo <amitayd@gmail.com> wrote:
>
>> Hi,
>> I'm trying to come up with a test for expected
>> MediaElementAudioSourceNode  output behavior.
>> However, I'm not sure what is the preferred way to test it as a unit,
>> without testing other components as a side effect.
>>
>> Some approaches:
>> 1) Using OfflineAudioContext as in the current Web Platform Audio test
>> (
>> https://github.com/w3c/web-platform-tests/blob/master/webaudio/the-audio-api/the-gainnode-interface/test.html
>> )
>>
>> 2) Using an Analyser node (preliminary test at
>> http://jsfiddle.net/UbHHr/8/)
>>
>> 3) Using a ScriptProcessor node (preliminary test at
>> http://jsfiddle.net/Jqmr2/12/ ).
>>
>> I want to to limit as much as possible depenencies in other components.
>> Would be happy to hear your thoughts and suggestions.
>>
>> Cheers,
>> Amitay
>>
>> P.S. This is a test I find important right now, since In firefox
>> nightly and older webkit browsers (i.e. Safari 6) connecting a
>> MediaElement source to either ProcessorNode or AnalyserNode does not
>> yield expected results.
>>
>>
>