Handle real root case better in Biquad tailtime computation
When computing the tail time for a BiquadFilterNode, we forgot to take the absolute value of the largest root when computing the tail. For the test case from the bug, the root with the larger magnitude was negative. Also, the computation of the larger root was incorrect; fix that. And the comments for the real root case was incorrect and wrote "r" when it should have been "r1". Manually verified that the test file causes a DCHECK failure in a debug build without this CL. Bug: 829349 Test: webaudio/BiquadFilter/biquad-829349.html Change-Id: I028331670a61da22a6f42bb7213869dc4cacf8ad Reviewed-on: https://chromium-review.googlesource.com/998518 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by:Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#549195}
Showing
Please register or sign in to comment