View Single Post
Old 11 October 2016, 23:49   #15
Dr.Venom
Registered User
 
Join Date: Jul 2008
Location: Netherlands
Posts: 278
Quote:
Originally Posted by Toni Wilen View Post
winuae.7z is from yesterday. Perhaps you got cached copy or something?
Indeed, I had to empty Firefox cache before it would download the new one. Strange, first time that has happened..

Quote:
Originally Posted by Toni Wilen View Post
Updated. Now if shared mode and requested buffer size is >= 10ms (Pre-Windows 10 default WASAPI buffer): use normal AudioClient->Initialize(), if < 10ms requested (currently only if buffer 1/2, possibly 3 too or new "min" option), AudioClient3->InitializeSharedAudioStream() is used.

"Min" buffer option added that selects smallest driver supported buffer size.

WASAPI buffer scale adjusted: for example size 5 now is old buffer size 4 and so on. Pull mode is much more stable than push, there is now less need for very big buffers.

It "sounds" like exclusive mode is not really needed anymore unless you want absolutely smallest latency possible.
I just finished a few rounds of testing and this WASAPI implementation is working very very well. For me this is the best version yet. Thanks for putting in the effort for this improvement, much appreciated .

Currently it runs seemingly flawless in low latency vsync mode, i.e. no pull overflows, for the realtek chip (with MS High def driver) with Setting 2 / BUF=352 and for the esi juli@ card with BUF=528 (minimum reported "PeriodInFrames" 480, I guess the card would really need a driver update to support this new Windows 10 Wasapi small buffer feature).

With BUF=352, is it possible to tell what the total latency approximately will be, is it 704/48000=~15ms?

WASAPI: Shared Pull CH=2 FREQ=48000 BUF=352 (704)
Dr.Venom is offline  
 
Page generated in 0.05161 seconds with 9 queries