I have posted about this before, so please accept my apologies. I am about to send this to Cakewalk support, but bearing in mind the backlog I have read about, I wanted to “copy in” the forum community.
Issue: In many Sonar Platinum projects, I am experiencing audible crackling/interference when my mouse cursor moves across VST GUIs.
System: This is a new HP all in one 27 inch PC. I have had it four months. Windows 10, Intel core i7 6700, 16GB RAM. Two graphic adapters – AMD Radeon R7 A360 and Intel HD Graphics 530. Audio interface is a Focusrite 1
st generation 6i6.
The machine was bought off the shelf, but I have tweaked it in accordance with Focusrite’s suggestions here (1 to 6 only – not done any “Advanced optimisation”):
https://support.focusrite.com/hc/en-gb/articles/207355205-Optimising-your-PC-for-Audio-on-Windows-10 Background: About three weeks ago I bought my first ever Waves plugins – L1 Limiter and Greg Wells MixCentric. I noticed the crackling sound as I moved the cursor over these two plugins, so I contacted Waves technical support. They took control of my machine remotely for two hours, and tried a complete reinstall of both Waves Central and the plugins in question. Both graphic adapters’ drivers have been updated to the latest versions. They tried disabling one graphics adapter and then the other. They ruled out interference from my remote mouse. We have tried increasing the buffer size on the Focusrite to very high levels (10ms+ and 442 samples).
The problem has got worse, in that the crackling now often happens with non-Waves plugins – e.g. the Sonitus range. The problem is NOT there if used in a very simple project, e.g., if I export a single mixed wav to a separate project and then use the two Waves plugins to master it, there is no crackling whatsoever. However, in a project with say 5 or 6 audio tracks, Addictive drums and EZKeys running, and a few effects, then the problem is there. However, the performance indicators in Sonar show very little CPU usage, and only about 25% of the memory is being used.
Finally, in the last few days I have downloaded
Tracktion 5, with the sole purpose of testing this issue in another DAW. I have imported a project from one of the Sonar projects I was having these issues with, into Tracktion. The problem does not exist in Tracktion.
Thanks for reading.
Bill