View Single Post
Old 04 December 2016, 22:19   #61
Registered User
Join Date: Aug 2004
Posts: 2,823
You could run something like LatencyMon to see if any device drivers are responsible for disabling interrupts for a long time. For me Intel wireless card drivers were a culprit, so using wired Ethernet instead would reduce the chance of pull overflow/crackling with small buffer size.

All the vsync modes require a significantly larger buffer size to be overflow-free here. I don't know whether there's any scope for improving that (series of small delays servicing audio in between each, instead of one longer delay???), but don't use vsync if you want the lowest possible buffer sizes to be glitch-free.

Windowed, WASAPI EX 48kHz on Windows 10 1511:
No vsync: can use buffer Min (128), no pull overflow messages.
Low-latency vsync: need sound buffer 3 (512) for no pull overflow messages.
Legacy vsync: need sound buffer 4 (704) for no pull overflow messages.
Variable sync: can have sound buffer Min with no pull overflow messages, but sound is very glitchy/crackly. Buffer 3 (512) seems mostly crackle-free. (My laptop doesn't support variable sync so that's probably why crackling but no pull overflow messages.)
mark_k is offline  
AdSense AdSense  
Page generated in 0.05898 seconds with 9 queries