So who went and marked the thread solved? I didn't [scratching head]

There is at least one host and CW staff with the ability to make silent edits, I am not one of them. When I alter a user post in any way, it will show that I made the change.
 
Was the issue resolved?

The clock has drifted so far, even user silent edits are almost impossible, see the above post where I made an edit to my own post in less than 2 minutes after the original post.

joden
So who went and marked the thread solved? I didn't [scratching head]

Good question. My question: Is it solved?
 
I just started having a very similar -- actually, identical -- problem, and pressing "E" to disable all effects did not fix it. Tomorrow I think I will simply delete all the plugins I was using and see what happens. I often add plugins before I'm finished tracking, because I want to get an idea of what the mix going to sound like. This is the first time I've had this happen.

Do you have WiFi on your system?  This is a known potential issue, where folks have had to disable their WiFi adapter drivers or physically turn off WiFi (if there is a switch to turn it off), then they can launch Sonar without DPC Latency spikes.  They turn on WiFi after finishing their Sonar session, and all is well.
 
Another potential is regarding antivirus software - or possibly some other background service, adding a bunch of DPC Latency.  Try suspending your antivirus software just before launching Sonar, and enabling it again after finishing your Sonar session.
 
Bob Bone
 

I agree about putting "SOLVED!" on a post ... it's deceptive.  Makes the casual viewer think it was just operator error, when usually, as here, it's a mixture of insufficient knowledge or inadequate documentation or design choices that are not clear.     Reading threads like this can be informative, and the "Solved" label is kind of a dis-incentive to read them.  
 
I for one didn't understand the thing about latency on a plug-in affecting everything, even if muted or disabled, except if archived. 
 
And how, by corollary, archiving a track that has such a plug-in will suddenly change the whole latency picture ... surely leading many a user to frustrating issues of things that used to match up no longer matching.

williamcopper
I agree about putting "SOLVED!" on a post ... it's deceptive.  Makes the casual viewer think it was just operator error, when usually, as here, it's a mixture of insufficient knowledge or inadequate documentation or design choices that are not clear.     Reading threads like this can be informative, and the "Solved" label is kind of a dis-incentive to read them.  

It would appear adding "[Solved]" was not a sufficient dis-incentive this time. It should neither encourage nor discourage the interested reader. It does add a piece of information about the subject that some may find useful.
 
In this case, the resolution was the user's choice of plug-ins. In order for certain plug-ins to work correctly, their input must be buffered. It is well documented and has been discussed on this forum for years.
 
Your conclusion about PDC recalculation is just wrong. Fortunately PDC recalculcation does not result in

williamcopper
 leading many a user to frustrating issues of things that used to match up no longer matching.

I go right to the SOLVED ones. It may save me some time in the future...

 

williamcopper
I agree about putting "SOLVED!" on a post ... it's deceptive.

 
Deceptive? What the hell?!?
 
I marked it solved because the OP said "Well I think I have narrowed it down the the LP-64 EQ  - every time I insert it into ANY track, the latency happens, remove it and it goes back to normal. As I said it doesn't even need to be in the track being recorded. Weird!!"
 
"Solve" means "find an answer to, explanation for, or means of effectively dealing with (a problem or mystery)." Read what the OP said. That is EXACTLY the situation. An explanation was provided, an answer was found, and that answer provided a means of dealing with the problem. 
 

Makes the casual viewer think it was just operator error, when usually, as here, it's a mixture of insufficient knowledge or inadequate documentation or design choices that are not clear. Reading threads like this can be informative, and the "Solved" label is kind of a dis-incentive to read them.

 
I disagree as much as it is possible to disagree. First of all, it's ridiculous to think that saying "solved" implies a value judgement that something was operator error. See the definition above. Second, and the reason for changing a thread title to include "solved," is that putting solved is an INCENTIVE to read it because if you have ever experienced this issue, you can see that there is a thread with an answer. Also, adding [Solved] means that anyone with basic search chops can use the magic string:
 
site:forum.cakewalk.com [solved]
 
To return hits that are chock full of tips. And if someone has this issue, this will make it much easier to find a solution.
 
I suspect I'm not the only person who scans the forum for threads that are marked "solved" so I can build my personal knowledge base about solutions to problems for future reference.
 
Accusing "deception" seems like a very strange conclusion to reach about something that's done to make it easier for people to "find an answer to, explanation for, or means of effectively dealing with (a problem or mystery)." Most people remember, and are courteous enough, to add this themselves. As long as an OP finds a solution to a problem, and states they have found a solution, I will continue putting [Solved] in the title to benefit other users. 
 
I might add that I'm always appreciative of people who circle back into a thread and indicate when a problem has been solved. Particularly in the case of operator error, some people are too embarrassed to return to the thread and confirm that something was their fault, and not a flaw with SONAR as they sometimes claim in their OP. Therefore the thread is never marked "solved," thus making it that much more difficult for someone making the same error to find a solution. 

And by the way, this post explains another very good reason for adding "solved."