© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
(In reply to comment #120)
> Please just leave these two bugs open and help motivating someone to work on
> it. Putting both topics in one bug only clutters this one.
Leaving two bugs open for the same problem doesn't make sense, hence the closed DUP.
> Don't rant against much needed progress in LINUX/Unix. And yes, PulseAudio is a
> big step in the right direction.
I personally think Pulseaudio does it the wrong way, but whatever. It's there and people are using it.
What we DON'T need on this bug are more posts saying "Pulseaudio is awesome for these reasons". It's a waste of time, energy, space and emails. No matter how awesome it is for whoever, support won't magically appear without patches.
Sure, there are the winepulse driver patches here, but consensus of established devs seems to be that it's the wrong way to go about it, and that the existing winealsa code should be made more Pulse-friendly. For anyone new to this thread, *that* is what is meant by the "Wine should support PulseAudio" summary. Only once that has been proven impossible should a winepulse driver be considered.