Closed Bug 1134258 Opened 9 years ago Closed 9 years ago

Investigate using server-side resampling for WASAPI on Windows 7+

Categories

(Core :: Audio/Video, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: padenot, Unassigned)

Details

This is apparently possible, see [0]. I don't know the quality of the resampler (in terms of audio quality and processing speed), though, I'll have a listen.

This can have a couple benefits:
- It lowers the CPU consumption of the client process (here, the firefox content process, or firefox process if e10s is disabled), so firefox is going to get less AUDCLNT_E_CPUUSAGE_EXCEEDED, and will be able to have more streams opened in parallel
- The mixer will be able to be smarter than we are: it can mix down several streams, and then resample the output of the (sub-)mixer instead of resampling each stream and summing them like we do (this is how kmixer with winmm works and is actually specced in some document on MSDN, I'm not sure if the same behavior applies with WASAPI).

We would just fall back on the codepath that uses the speex resampler on Windows Vista.

[0]: https://msdn.microsoft.com/en-us/library/windows/desktop/dd370791%28v=vs.85%29.aspx
No I misread something in the docs, this is sadly still not possible.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.