[Bug 10495] Wine should support PulseAudio

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=10495





--- Comment #99 from Lev Abashkin <kyle1.schrecknet at gmail.com>  2009-06-16 07:31:24 ---
(In reply to comment #98)
> Please carefully re-read all the comments in this bug report from the very
> start.

Just did it. There are 2 types of comments here:
1) From users who got their stuff working with winepulse.
2) From developers speaking about a)hardcore gaming and b)redundant code.

a)References to "hardcore" gamers make me smile, they use Windows or native
games. Btw didn't Vista bury DirectSound?
b)Technically you are right, there is no reason to make something already done.
There is very interesting comment #89 pointing to
http://www.winehq.org/pipermail/wine-devel/2009-June/076112.html.

Quote: 
>> > First, I talked with a Pulseaudio expert about what we can do to make
>> > things work better.  He said that if we want good compatibility we will
>> > need our ALSA stack to use the Pulseaudio safe subset:
>> > http://0pointer.de/blog/projects/guide-to-sound-apis.html. I've filed a
>> > metabug tracking this here:
>> > http://bugs.winehq.org/show_bug.cgi?id=18740.  Use of this unsafe subset
>> > can cause most problems with stuttering or even complete dropoff.

So, your opinion is that someone has to rewrite ALSA stack in Wine to close
this bug. Fine. Any ideas when? 
Why not to use native backend when it solves the problem? End users are
interested only in convenience and stability.

<offtopic> I wonder why all the ancient sound backends still live in the code
tree. Doesn't ALSA and Jack cover all user needs? <offtopic/>

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.