Windows 10x64. Dell Vostro i5 with Cirrus HDA. 16b/44K1.
GetDevicePeriod() reports default 101587ns and min 29025ns. GetBufferSize()
returns 448.
Once the render thread is up and running it gets signalled that data is
ready. GetCurrentPadding() is called before GetBuffer() - the former reports
a value of 448. Does this mean the render has stalled?
If there is an entire buffer waiting why is a data ready event signalled at
all?
Out of interest I tracked the number of data events against the count of
instances where GetCurrentPadding() == GetBufferSize() and it seems to
happen each time.
Shared mode works perfectly. The render thread successfully calls
AvSetMmThreadCharacteristics() on entry. Does the application itself need to
raise its own priority as I dimly seem to recall from the days of KS mode?
TIA
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
