http://bugs.winehq.org/show_bug.cgi?id=28723
--- Comment #91 from Andrew Eikum aeikum@codeweavers.com 2011-12-16 09:11:51 CST --- (In reply to comment #89)
This is the 0000 patch to compute period and duration limits like native does. I'm going to submit this tomorrow (adding OSS and MacOS). It will end the if(!period) issue. It requires a rebase & editing of the remaining 3 patches.
Looks good, thanks.
We haven't heard from Alexey in a little while. If we don't hear from him by Monday, I'll send patch 2 in my name with a note crediting him for the algorithm.
(In reply to comment #90)
I put back set_period_near into the last patch. But I'm not satisfied with the results. My render test produces a spurious xrun notification with plug:dmix that disappears when running with full logs or when using set_period_min. Where does that xrun come from? OTOH, set_near allows PA to produce better position values in Intrepid. Oh well, it really looks like min&max is not over yet.
What about first setting _min(3*period) and then _near(3*period)? Then we get our desired minimum and set the size hint as well.