This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 19704 - Acceptable range for value of AnalyserNode's fftSize
Summary: Acceptable range for value of AnalyserNode's fftSize
Status: CLOSED FIXED
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC Windows 3.1
: P2 normal
Target Milestone: TBD
Assignee: Chris Rogers
QA Contact: public-audio
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-25 16:08 UTC by Olivier Thereaux
Modified: 2013-04-25 15:37 UTC (History)
0 users

See Also:

Attachments

Description Olivier Thereaux 2012-10-25 16:08:44 UTC 
We discussed about FFT value back in May, and resolved that it was OK as a power of 2, rather than being an arbitrary value:
http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0506.html

We have however not addressed a related question about the value range for the FFTSize. 

Raised by James on 22nd March:
http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0460.html
and documented in an action item:
https://www.w3.org/2011/audio/track/actions/41

[[ For fftSize in RealtimeAnalyserNode in the spec, it only says the value must be power of 2. But in fact in the implementation, the value must be limited in the range of [128, 2048], and it will throw the exception if illegal value of fftSize is set. Which should be documented in the spec. ]]
Comment 1 Chris Rogers 2013-04-08 21:52:07 UTC 
Fixed:
https://dvcs.w3.org/hg/audio/rev/7e5e69ce9ad8
Comment 2 Olivier Thereaux 2013-04-25 15:37:52 UTC 
Changeset looks good. Closing.