Comment 198 for bug 371897

(In reply to comment #92)

> 1. this will never be committed to WineHQ (the reasons are mentioned
> numerous times in this bug)
Only comments against the _inclusion_ of such a driver are:
comment 4 - assumes the cassical view of audio hardware (what about USB? Bluetooth headsets? Networked? Hotplugged? Device change-on-fly?)
comment 6 - assumes that the only use of wine is for games. What about media players? Audio development environments? Telephony/VoIP?
comment 52 - claims non-existent or non-factual previous comments as proof

"Serious gamers" can always continue to use direct alsa. This is in no way changed by the inclusion of a pulse winmm driver.

The text of this bug is "Wine should have a PulseAudio output plugin" not "Wine should clean up its alsa code"

Using a pulseaudio wine driver it is easy for me to capture audio from live playback or hardware inputs by recording software. This is not easy under alsa. Multiple stream instances per device in both directions are supported. Easy network transparency, better hardware buffer control, better volume control. All are possible.

I personally have been contacted by many wine users who have championed my efforts and offered support. I cannot believe that a project the size of wine would allow the misguided best interests of few to alienate users.