Hey guys:
 
I installed Cambridge about a week ago and ever since I've had clicks and pops lick crazy.  I get them even running one audio track or VSTi with latency set to 256.  Yikes!!  Anybody else experiencing this? Any thoughts on what causes them?  The previous version of Platinum did fine. 
 
Thanks.

I've always associated pops and clicks with the audio drivers. try different drivers, get updated drivers.
see if they go away with MME setting...   

jude77
Hey guys:
 
I installed Cambridge about a week ago and ever since I've had clicks and pops lick crazy.  I get them even running one audio track or VSTi with latency set to 256.  Yikes!!  Anybody else experiencing this? Any thoughts on what causes them?  The previous version of Platinum did fine. 
 
Thanks.

Yep, I'm getting the same thing. I've tried changing latency and can get rid of the clicks but when recording I'm experiencing huge synch issues.
 
It's a no win situation.

There is a thread in this forum by Craig Anderton that tells you a little known tweak to Windows that does wonders for eliminating this problem. Do a search here and you should find it. I'm sorry I don't remember what it was but it relieved me of most of my problems.

The other possible solution is to delete (or rename) the AUD.INI file and let Sonar create a new one. If something in the engine has changed, a new AUD.INI will allow Sonar to recalibrate itself to your audio interface drivers.
 
Regards,
Dan

What Driver Mode are you running in Sonar?
 
Also, do you have any effects loaded in the project having the audio glitches?
 
Do you use ASIO4ALL, or have it installed even though you are now using a dedicated audio interface?
 
What sort of audio interface are you using?
 
Do you possibly have WiFi present on the computer this is happening on?
 
Sorry for all the questions, but I want to get up to speed on the above, to help me understand areas where some changes might help the situation out.
 
Bob Bone
 

robert_e_bone
Sorry for all the questions, but I want to get up to speed on the above, to help me understand areas where some changes might help the situation out.

I would agree with taking the approach that the issue is probably due to some other coincidental change in the environment that has increased DPC latency or is interfering with interface driver or something like that, rather than being a direct result of updating to Cambridge.
 
In addition to answering Bob's questions, I would suggest you check DPC latency, and make sure SONAR is not set to Share Drivers - at least for the time being. Renaming AUD.INI as Dan suggested would also be a good troubleshooting step. 
 
Does SONAR's Performance module show normal and balanced CPU core usage?
 
 
 
 

Hey Guys:
Many thanks for your help and replies!!
To answer your questions:
 
1.  I'm running ASIO with NO Asio4all (never installed it even).
2.  This happens without any effects present.
3.  My interface is a Roland Quadcapture.
4.  I do have wifi on this computer.
5.  Performance is balanced across the cores.
 
Again, many thanks for your help and interest!!

OK - Many many many many lots of folks have issues running Sonar with WiFi on.  It tends to spike DPC latency, causing all manner of audio grief.
 
Fortunately, there is an easy fix for the above - just before you are going to launch Sonar, turn the WiFi off (there is sometimes a physical switch or function key to do so), or disable the drivers for it in Windows Device Manager.  Then, launch Sonar, and after finishing your Sonar session and closing Sonar, simply turn the WiFi back on or enable it again.
 
Now, there may be something else entirely that is causing your issues, but the above is a simple and quick test, and possibly fix, so please try the above and post back with results.
 
Bob Bone
 

Hi Guys:
 
I disabled wi-fi, but no improvement, the pops continue.  Any other thoughts?
 
Again, thanks.