Hi all!

I've been having a really annoying hard crash lately. It's totally reproducable and I've never seen anything like it before.

Everytime I try to move a clip Microsoft Visual C++ Runtime Library is getting a Runtime Error and SONAR hangs.



Specs:
SONAR X3c Producer
Intel Core i7 3770K @ 3.50GHz
16GB RAM
Windows 8.1 64-bit
Octa-Capture
VS-700C

I would really appriciate any ideas!

Best Regards
Ludvig

try downloading this and installing. maybe this will help.
 
 
Download Visual C++ Redistributable for Visual Studio 2012 Update 3 from Official Microsoft Download Center

Darn beat me to it.... although Visual studio 2013 came out today...

Hey guys!

Thanks a lot for your suggestions. Tried that but it did not change the situation.
Will try reinstall tonight.

Any other ideas more than welcome!

Best Regards
Ludvig

I also got this message twice. when using prochannel.Installing the net framework update did not help. I opened another thread with crashes when moving bus faders when prochannel modules are present on it.

I believe this to be a newly discovered programming error in Sonar.
 
If running X3c, you may try reverting to X3b, until this gets addressed.  If the problem lies within X3b, you might consider reverting to X3a, but doing either of these does raise the potential for exposing additional bugs (reverting to 'b' negates any fixes that were made in 'c', etc.).  You have to decide what is the most beneficial path to follow.
 
To the Cakewalk developers:
 
http://support.microsoft.com/kb/125749
 
Bob Bone
 

Time to run windows update.

cowboydan
try downloading this and installing. maybe this will help.
 
 
Download Visual C++ Redistributable for Visual Studio 2012 Update 3 from Official Microsoft Download Center

I was under the impression to stick to what ever redistributable comes with the software when it is installed via its installation package. isn't that the one against which it was developed and tested?
 
If there is a problem in the underlying windows API that needs to be fixed via updating redistributables, I would assume it should be very much in Cakewalk's interest to let us all know rather than having us try these things blindly ...

The package that was delivered was tested with the redistributable that cake had to work with at the time.Since then there were updates to windows that cake has no control over. That is why it wouldnt hurt to try to update the redistributable to see if that solves the problem.

Software has dependencies everywhere. If you think you know how it is all hooked up together and everything must be logical you probably don't. I.e. Sore foot? Must be a muscle! Then you find out it is your brain.
 
Even Sonar is liable to bugs that Microsoft may supply when it is built and compiled, and as Bob duly pointed out, it could be a programming error, and it could actually be a Microsoft programming error that may be corrected via windows update or updating software elsewhere. Yes it happens.... and yes it could be Sonar. But you have to rule it out.