Gerard O'Driscoll
December 6th 03, 09:58 PM
It seems that under Windows XP, waveIn sleeps for 100msec
and then checks if any input buffers are complete and
signals an event to the application if there are. This is
not the same as under Win2K where the event is signalled
immediately when the buffer becomes complete.
In my audio driver under XP, I call PortStream-
>ReleaseMapping when the audio buffer is completed, but
this does not immediately cause the app to get the event
signalled.
The result is that the app gets woken up every 0msec,
100msecs or 200msecs, even if buffers are being filled,
for example, every 120msec.
Has anyone seen this or got a fix?
Thanks.
and then checks if any input buffers are complete and
signals an event to the application if there are. This is
not the same as under Win2K where the event is signalled
immediately when the buffer becomes complete.
In my audio driver under XP, I call PortStream-
>ReleaseMapping when the audio buffer is completed, but
this does not immediately cause the app to get the event
signalled.
The result is that the app gets woken up every 0msec,
100msecs or 200msecs, even if buffers are being filled,
for example, every 120msec.
Has anyone seen this or got a fix?
Thanks.