This happened a few times now in one project so far. I hadn't had any issues with this project before.
A little background:
I've been having the issue of Sonar using a lot of CPU and getting bad crackling etc. There is a recent thread on this with Lexington update.
http://forum.cakewalk.com/Lexington-using-more-CPU-No-problems-now-crackling-Perf-Module-CPU-is-very-active-m3346937.aspx
Anyway I decided to un-install X3e and SPLAT and do a clean install of just SPLAT. All went pretty well except somehow Sonar still found some of my settings. not sure how, I deleted everything i could find. The CPU issue is still an issue.
In the project that I am getting this error I noticed the project won't play and freezes for a moment and seems to have recovered untill I try to play it again. This keeps happening like going in circles. The project doesn't white out or anything just keeps getting this error. So far I haven't had this issue with another project so just wondering what the error is.
 
Thanks

This is a long shot.
 
While debugging our control surface code I have the option to "Attach to a Process" in the debugger.
If a file is loaded into Sonar, the process "Title" for the Sonar Process is HUDNow and has been since the skylight interface of X1 I think.
 
It likely refers to the main UI thread loop in Sonar but only the bakers know for certain.
 
In any rate, It does not refer to a HUDNow vst or something else YOU did. It just refers to the process thread that was executing when all it all went south. Could just as easily be called SonarMain or something.
 
:Ron

bitman
This is a long shot.
 
While debugging our control surface code I have the option to "Attach to a Process" in the debugger.
If a file is loaded into Sonar, the process "Title" for the Sonar Process is HUDNow and has been since the skylight interface of X1 I think.
 
It likely refers to the main UI thread loop in Sonar but only the bakers know for certain.
 
In any rate, It does not refer to a HUDNow vst or something else YOU did. It just refers to the process thread that was executing when all it all went south. Could just as easily be called SonarMain or something.
 
:Ron

Thanks for the reply Ron. I don't know what your saying Lol but I appreciate it.

You're welcome.
I prolly don't know what I'm saying either. :-)

hay ...
I have the same problem and i do not know how to solve this.... if you find any solution please tel me
 
 
thank you so much