Correlation does not equal causation but it does hint that perhaps MSE isn't quite as non-intrusive as some people would have us believe. Just bringing this up because this is actually the first time I've pretty much been able to directly correlate a functionality problem with Sonar in relation to MSE. Tada! Still it did not seem to interfere with the actual performance of Sonar but I have a high powered rig. Sonar opened up REALLY fast and when I loaded the project there was no whiteout. So I closed Sonar and reloaded the project. The MSE graphics kind of morphed into the X3 graphics and left graphical residue in the Sonar GUI. Just now I loaded my current project and got the usual lag/whiteout and because I had been online recently remembered that I had MSE turned on (and I had actually had it on for months without realizing it). I've done a bunch of stuff recently that I thought might clear this up (updated Windows, updated Sonar.) but was still getting the whiteouts. I had however been getting brief whiteouts in X3 when loading a project. I used to pretty much always leave it disabled but have been having such good luck with X3 I've kind of been letting it slide and leaving the MSE Real Time Protections on. Just thought I would mention this because I've heard many times that MSE won't really interfere with a DAW.
A note about Microsoft Security Essentials and Sonar: Turn it off.
0 kommentar(er)
