https://bugs.winehq.org/show_bug.cgi?id=30639
--- Comment #37 from Andrew Eikum aeikum@codeweavers.com --- (In reply to winetest from comment #36)
Since wine is fixing regressions now how likely would it to have this fix in wine 2.0?
Or is it too complicated to test? Or some other issues?
This bug was caused because we implemented a high quality resampler, which simply requires more CPU power. The patch in staging turns down the quality of the resampler if there are more than 4 buffers to resample. This kind of works, but if I have a high end CPU, I'd rather get the high quality.
I think a smarter heuristic might have a better chance of getting in. For example, we could time how long resampling takes, compare that to the period length, and lower quality if a large percentage of the period is spent resampling.
Another option is to increase the efficiency of our new resampler so it works on older CPUs.
In any case, no such patch exists, and this problem will largely solve itself as users get better CPUs, so it isn't terribly high priority.