Re: My New Build
Originally Posted by
John Ludlow
No. One more.
Today I discovered something that I'll bet many of you already know: if you left click on the "Load" text readout a new window temporarily pops up that lets you know how many slipped (not dropped) buffers have occurred since SAC last went live. I am not the sort of user who reads the manual cover to cover. Rather, when I don't already know how to do something - I search the manual looking for it. I searched for 'dropped' buffers and didn't find anything.
I did all my previous tests with only a subjective idea of whether there were dropped buffers. Just on a whim today I searched the SAC manual for 'slipped' buffers and now I know how to measure them. This is a very useful feature.
Yes, slipped buffers and dropped buffers for your purposes are the same thing.
They occur when the audio engine doesn't complete processing of the buffer data, before it has to fetch the next buffer.
Changing to 1x64 will likely get you to zero slipped/dropped buffers.
I have personally found that shifting SACs processor affinity off of CPU core 1 to also have an impact on slipped buffers, as there are a lot of OS related processes vying for time on CPU 1.
Also, again make sure that SAC is running in real-time mode. It won't do that by itself running on Win10 even if set to real-time mode in SAC menu unless SAC is running as admin, or you force it to real-time mode in Process Lasso.
I personally have been doing that assignment in Process Lasso so I don't have to run SAC as admin.
In my testing under Win10 it appears that you can launch multiple versions of SAW/SAC when run as admin, that doesn't occur when run as a standard user.
Last edited by cgrafx; 07-25-2019 at 07:02 AM.
---------------------------------------
Philip G.
Connect With Us