Hi,
Andrew Eikum wrote:
>Then, GetCurrentPadding() returns "write - read" and GetBufferSize() returns
>the queue size limit.
>As far as I can tell, this is entirely consistent with how Windows behaves.
I added some lines to mmdevapi/tests/render.c to find out more about
mmdevapi with the help of
On 06/01/2011 07:33 AM, joerg-cyril.hoe...@t-systems.com wrote:
The problematic situation is when avail is small, as the following sleep for
half a
buffer size in MSDN's example will inevitably produce an xrun.
So what actually is the buffer size and how does GetCurrentPadding behave?
I don't e
Hi,
I have one big concern about MSDN's "Rendering a stream" (shared mode)
example w.r.t wrap-around of buffer pointers and how Wine implements it.
The example is at
http://msdn.microsoft.com/en-us/library/dd316756(v=vs.85).aspx
Suppose the write pointer is near the end of the buffer and the app
