© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
(In reply to comment #171)
> > Personal opinions about PulseAudio aside, the way to get a PulseAudio driver
> > into Wine would be to first fix Wine's audio driver architecture, and implement
> > the driver afterwards.
>
> Why would the first part be a prereuisite?
>
Because the current architecture doesn't scale that well. You're free to try of course, but I think you'd have a hard time trying to make a convincing case to Alexandre that that part can be skipped. Realistically, I don't think that requirement will go away anytime soon.
Doing that part would also make a more convincing case that you (whoever would implement it) know what you're doing, which would make the second part more likely to go in, but that's secondary here.
> Sure, it's the nice way of doing it, but there are people waiting to use Wine.
> Those would really apreaciate a stop-gap solution like the working, existing
> winepulse.drv.
Well, winepulse.drv exists, it's just not supported by the Wine project. That creates issues for people reporting bugs while using it, but that's the trade they make.