winealsa: Stop may not use snd_pcm_drop or lose written frames.

[Joerg-Cyril.Hoehle at t-systems.com]

Hi,

we talked about this issue a couple of times.  I had not submitted it after the "limit ALSA writes
to 3 periods" patch because its effect became hardly noticeable by my tests.  However, the new
capture tests again clearly show it's wrong.  Furthermore, I'm still thinking about implementing
a different rendering algorithm that would allow to write more than 3 periods.

Another objection may be that it does ALSA/PA good to reset it sometimes.  Now we simply
let it enter underrun state. A variant behaviour would be to use snd_pcm_drop unless in
running state, but what would drop/reset change in such a case?
If we want to reset ALSA, we should start adding IAC_Reset or
WaveOutReset. Stop is not appropriate.

Regards,
 Jörg Höhle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-winealsa-Stop-may-not-use-snd_pcm_drop-or-lose-writ.patch
Type: application/octet-stream
Size: 1250 bytes
Desc: 0001-winealsa-Stop-may-not-use-snd_pcm_drop-or-lose-writ.patch
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20120112/eb401fb6/attachment.obj>