Closed Bug 1266737 Opened 9 years ago Closed 7 years ago

Some Web Audio FFT results unexpectedly need to be scaled by two

Categories

(Core :: Web Audio, defect, P4)

Product:
Core
Component:
Web Audio
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1424906

People

(Reporter: dminor, Unassigned)

Details

There's a note in FFTBlock.h about results being scaled by two for compatibility between libav and kissfft/openmax [1]. I ended up having to add a scaling factor of two to make the "unscaled" version of the inverse FFT routine in Bug 1158741 work. Now when adding a test case for the unnormalized PeriodicWave in Bug 1265405 I ended up having to add another scaling factor of two to make the test results work out. This seems wrong, but it's quite possible I'm missing something here. [1] https://dxr.mozilla.org/mozilla-central/source/dom/media/webaudio/FFTBlock.h#113
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
It appears that problem is actually that PeriodicWave unexpectedly needs to be scaled by 0.5.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.