![sonar 8.5 dropouts sonar 8.5 dropouts](https://c.scdn.gr/images/sku_main_images/006369/6369758/xlarge_20150317114137_soundcraft_signature_12_mtk.jpeg)
I purchased the Babyface but had huge problems with latency and was unable to set buffer size below 1024 in order to get rid of cracks, pops and dropouts, which was ridiculous especially because I have a top high end PC (I7 980 6c, Win 7 64.) Hey there, hope I can help many of people experiencing latency problems with soundcards.
Sonar 8.5 dropouts drivers#
Absolutely ridiculous, I have to download updated drivers for my notebook from other companies like Toshiba and HP, as Dell stopped with outdated Vista drivers on this one a year ago, that is about half a year after its first shipment. Dell's earlier fix on this had been incomplete. Just a side note for Dell users: I am 100% sure that these ACPI calls are caused by the motherboard/BIOS. So like said before, this tool might help a lot more than DPCLat in many cases, giving more information on where to look for the problem (and I give it the thumbs up), but it will still fail in some situations. Well, it could have said 'Dell Studio' instead, this information is simply useless and does not point anwhere to solve the problem (Timur - same in XPerf?). The higher spikes (up to 5 ms) are identified as ACPI.sys. Note that ndis.sys is most probably not the culprit, it is the network driver from the network adpater that needs to be improved (Broadcom here). So LatencyMon tells me the lower spikes are caused by ndis.sys. My Dell has lots of different spikes between 1 and 4 ms. I had no time to check the cumbersome XPerf, but Timur might be able to tell us if XPerf would bring even better results, because the information shown in LatencyMon is still not the final solution in some cases.
![sonar 8.5 dropouts sonar 8.5 dropouts](https://cubaseindex.com/____impro/1/onewebmedia/cubaseindex_aduarzl2160919_Reverse313_314Xnview.jpg)
So far it seems this software is a big step forward compared to DPCLat, simply because it includes the information we have all been waiting for - what the *?&%$ is causing the spike. I tested LatencyMon with my crappy Dell Studio 1537.