Slipped buffers with SAC, SAWStudio and Win10 is still a mystery... Win10 is a bear for this kind of realtime stuff...
I believe SAC is accurately reporting when its threads get stomped on and it fails to finish a buffer load... but you still have SAWStudio filling its buffers and then handing them over to SAC... there is currently no measuring mechanism in that part of the chain... so I am looking into the fact that SAW may be getting starved from time to time as Win10 happily processes its 100+ background processes and there is no direct way of measuring whether it is not finishing its internal load in time... I am exploring some new code to be looking for unfinished buffer loading on the SAW side of the link.
I have made modifications to SAC's engine that moves a few more routines under the Time-Critical thread umbrella... and this seems to have a positive impact on canceling out some of the Win10 thread stomps that can create the SAC slipped buffers... but now SAW starvation is even more pronounced and the end result may not be a good one.
Its all quite a tough challenge with the way Win10 attempts to override thread priorities and decides to load balance intense threads to give up time to lesser threads... this has made an attempt at realtime performance almost impossible... I'm still working hard at it to try and get around this behavior.
For now... I would recommend 64 size as the lowest buffer size, since 32 size definitely puts extra loads on the engine loop as the variable setup time for each loop starts to take longer than the amount of samples processed each time around.
You can try using some other playback source for your tests... or playback from SAW on a different machine and analog connect to your SAC machine... this eliminates the SACLink buffer handoff and will tell you pretty accurately whether the slippage is on the SAC side or the SACLink handoff side of the process.
In my tests... SAC can sit there sometimes for twenty hours with no slipped buffers... then instantly drop 20 or 30 buffers as Win10 decides to run some background process and stomp all over the SAC engine... I have spent weeks with monitor logging programs running in an attempt to narrow down exactly when the buffer slippage occurs and exactly what processes may have started or intensified when the slippage happens... it really is a horror story.
XP was so much more controllable... but alas... it is dead to the world now.
Bob L
Connect With Us