Comment 271 for bug 371897
Revision history for this message
|
|
#271 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
(In reply to comment #165)
> I think my previous statement wasn't quite clear. What I intended to say is
> that the only situation in which I'd favor a winepulse.drv is when nobody needs
> winealsa.drv because the pulse native API has become the a de-facto standard,
> and there's nobody who does not use PulseAudio.
> (I personally don't think this is likely to happen)
Why do you assume a need for dropping winealsa.drv?
If you really absolutely need to drop a driver to add a new one - drop the obsolete wineesd.drv in favor of the working winepulse.drv.
EsounD is EOL and PulseAudio is it's replacement. PulseAudio isn't going to go away, especially not on the large desktop distros - even Skype and Adobe accepted that one.
The patches are there, they compile, seem to work (at least here) and they are a solution to a realworld problem: Running Windows Games with sound hassle-free via Wine on a modern desktop distro like openSUSE, Fedora or Ubuntu. And, to be honest - those are the main targets for people switching from Windows. And Wine targets exactly those people: http://
Sure, when the new sound system hits Wine, all of that needs to be implemented again. But a good solution today is better than a perfect solution tomorrow - even if it's just a stop-gap solution.