http://bugs.winehq.org/show_bug.cgi?id=29294
--- Comment #57 from Jörg Höhle hoehle@users.sourceforge.net 2013-03-04 15:22:10 CST --- It's good that you found a working setup. Yet I tend to consider this extra Python middleware process a hack which is why I'd like to see logs from current wine, perhaps produced under both configurations: the naïve alsa_jack bridge and then the working setup.
cd dlls/mmdevapi/tests; rm /tmp/render.log; WINETEST_INTERACTIVE=1 WINETEST_DEBUG=2 WINEDEBUG=+tid,+timestamp,+alsa,+mmdevapi wine mmdevapi_test.exe render >>/tmp/render.log 2>&1
Does the sine wave sound good? What about comment #47, "So in Civ with the working sound, the click sound comes roughly 1/2 second afer it should play." Is that still the case or does "sound works ok now" in comment #56 mean that there's no such huge latency?
If you don't compile Wine yourself, you can obtain mmdevapi.exe either from testbot http://testbot.winehq.org/JobDetails.pl?Key=24482 until expired or from the daily test.winehq.org winetest.exe which is a sort of self-executing archive that'll extract all tests when invoked with /x IIRC, then run the mmdevapi one.