[Bug 10495] Wine should support PulseAudio

[wine-bugs at winehq.org]

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

--- Comment #288 from Raymond <superquad.vortex2 at gmail.com> 2011-01-08 00:53:54 CST ---
(In reply to comment #144)
> Probably the largest problem for audio in WINE is the WaveOut/WaveIn API's.
> Currently the WaveOut and WaveIn API's are the base for the other audio api's
> in WINE (except openAL.) The audio api, designed probably in the early 90s for
> PCs of the day seems to have been the first implemented in wine, and all audio
> api's fall-back to it (except openAL and DSound on OSS and ALSA in special
> occasions.) Probably the biggest pro-native-pulseaudio reason is the waveout
> functions. Through libalsa pulse, calls such as waveOutReset() and
> waveOutResume() require a reconnection to pulseaudio each call. Using a native
> pulseaudio driver we can write audio data into pulseaudio and do the pause,
> resume and reset calls without penalty.
> 
>

But alsa-pulse plugin also support snd_pcm_pause() 

http://git.alsa-project.org/?p=alsa-plugins.git;a=commit;h=d9a839d51255c939f394f770b249c8a4a9600122

do you mean that when winealsa use "pulse" plugin , waveOutReset() and
waveOutResume() using snd_pcm_drop() and snd_pcm_prepare() require a
reconnection to PA server ?

This seem explain why chips challenges (16-bits application) fail after about
10 minutes of gameplay when using pulse 

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

-- 
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.