Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
google_rtc_audio_processing: Correct floating point representation
Lionel corrected me: there was an off-by-one error in the math here. The desired analysis space for S{16,32}_LE formats maps -1.0 to the minimum (2's complement signed) integer value, and 1.0 to "one more than the maximum integer value" (so -1.0 is exactly representable, but 1.0 is not). This requires a clamping step be added to the code, but that's probably a good idea anyway given that the floating point output data (we're not longer using the wrapper inside the google library) may not itself be fully saturated. Signed-off-by: Andy Ross <[email protected]>
- Loading branch information