http://bugs.winehq.org/show_bug.cgi?id=29841
--- Comment #5 from Andrew Eikum aeikum@codeweavers.com 2012-02-09 08:40:57 CST --- Okay, thanks. By the way, what version of PulseAudio are you using? Would you mind gathering another log with the same channels and also ",+timestamp"?
My analysis so far is "I don't know." The ALSA device is reporting loads of underruns, despite us feeding it data. Possibly our timer to write data to ALSA is coming late (hence +timestamp). Possibly you're running into a PulseAudio or alsa-plugins bug.
If you're comfortable hacking code, you could try forcing winealsa.drv to use the "pulse" device by changing in <dlls/winealsa.drv/mmdevdrv.c>:
-static const char defname[] = "default"; +static const char defname[] = "pulse";
and rebuilding winealsa.drv. That might give you joy. (This is a known issue; Wine needs better device selection code.)
My reasoning here is this line from your log:
002e:trace:alsa:AUDDRV_GetAudioEndpoint Opening PCM device "default" with handle_underrun: 0
Coupled with the many underruns ("state 4", "avail: -32"). Given a pulse-backed device, I would expect "handle_underrun: 1", which might improve things.