https://bugs.winehq.org/show_bug.cgi?id=39814 --- Comment #13 from Andrew Eikum <aeikum(a)codeweavers.com> --- Actually, this might not be an application bug. Reaper tries to write in period sizes. This can sometimes fail due to clock skew, which is what I was seeing in the 60 ms case. In the failing case, our claimed minimum period size is unrealistically low, just one frame (1 / 48000 seconds). Reaper understandably can't handle that. Setting PULSE_LATENCY_MSEC causes winepulse to return a more realistic period size (1.6 ms) which Reaper is able to handle. I wonder if we should clamp this value to something more realistic. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.