-
Andrew Eikum authored
Now, winealsa maintains its own buffer, which is written to ALSA on the period cycle requested by the application. We also let ALSA start when it has enough data and stop when it runs out, recovering from the expected underruns. This seems to be more like how ALSA expects to be used.
b0652dd8
| Name |
Last commit
|
Last update |
|---|---|---|
| dlls | ||
| documentation | ||
| fonts | ||
| include | ||
| libs | ||
| loader | ||
| po | ||
| programs | ||
| server | ||
| tools | ||
| .gitignore | ||
| ANNOUNCE | ||
| AUTHORS | ||
| COPYING.LIB | ||
| LICENSE | ||
| LICENSE.OLD | ||
| Make.rules.in | ||
| Make.vars.in | ||
| Makefile.in | ||
| Maketest.rules.in | ||
| README | ||
| VERSION | ||
| aclocal.m4 | ||
| configure | ||
| configure.ac |