Comment 414 for bug 371897

(In reply to comment #202)

>
> > > *) patch is incomplete
> Supports WaveOut, WaveIn and Dsound playback and capture. All testsuite tests
> pass.
>

The current status is only support waveout ,wavein, dsound via wine specific wave_directsound

winepulse does not support midi , mixer

>> Or hardware-accelerated ALSA, which is disabled by pulse.
>Most audio hardware has no hardware accelerated mixing, which makes it
>difficult to implement hardware-accelerated mixing.

If pulseaudio take up the role of Kmixer in linux , winepulse should provide hardware secondary buffers like the Kmixer in windows

If you can select Full Acceleration using onboard HDA in XP and dxdiag play sound with software and hardware buffers provided by Kmixer

why onboard HDA cannot use Full Acceleration (i.e. hardware secondary buffers) with winepulse

There are differences between aplay , wine , dmix ,pulseaudio

the normal ALSA application set buffer size as stop threshold , the sound card stop playing/recording when xrun (underrun/overrun) occur.

both wine and pulseaudio server set boundary as stop threhold similar to dmix , this disable the automatic stop at xrun (i.e. dmix , wine and PA server are able to recover xrun by snd_pcm_forward() or playing silence ) since they cannot control when will the other application send the audio data

Base on past few years experience, the alsa developer already allow dmix to confugured a suitable buffer size and period size for normal use of those PCI sound card

But pa server and wine seem still experimenting to find the optimum buffer size / period size ( buffer time/period time)