I thought I had my Sonar Exception error crashing problem solved by moving my Toneport KB37 USB device to another port as someone suggested, I also moved it to a USB2.0 PORT instead of USB3.0 Port which someone else suggested.
Like I said : "I THOUGHT", it worked fine for a day or so, then out of the blue it crashed. It has gotten to the point for me that everytime I load up Sonar Pro which is what I have that it is stressful to try and record anything because of the fact that it crashes so often. Not to mention fresh Windows 10 Install's, NOTHING BUT SONAR AND WINDOWS 10 INSTALLED ON A FRESH INSTALL.
I hear users saying "OH It may just be a BUGGY PLUGIN, or PERHAPS Windows 10". If that is the case then why would Sonar say it's Windows 10 ready/compatible? I'm sure someone will chime in and say : "Well it means Windows 10 compatible but not your plugins". Well, here's a quick fact, these crashes I have been having were using plugins like TH3 Overloud and XLN AD2 Drums ONLY to create music with. And they were both purchased from the cake store. So if they aren't compatible then why sell them if they don't work properly.
I am really at my wits end and I have to be honest, I would prefer to use Sonar and support cakewalk, but there are multiple reasons why I don't believe I can do so anymore, mostly the crashes, but for one thing is the fact that I purchased Sonar Pro in good faith that it actually worked properly, because of various reasons, some health, work, etc.... I could not properly test it. Now I'm in a situation where I get around to start using it and the updates for FIXES AND TECH SUPPORT are over with. So reporting the FAILURES when it crashes like I have done over and over are completely a waste of time for me because "I GUESS IT IS MY FAULT IT CRASHED".
As for the WINDOWS 10 Being the problem, or BUGGY PLUGIN, like so many keep saying, come to find out that is not the case.
This post will probably get deleted but I installed and started using Reaper 2 days ago, it took a little while to get it setup, but I have had ZERO CRASHES!!! Most of the Sonar Plugins work with it, some a little differently like Melodyne and AD2 drums and such, while some others don't work at all like the Nomad plugins, but quite honestly I don't need none of those that don't work.
I'm not posting this to KNOCK SONAR or CAKEWALK! Don't get me wrong, I would prefer to use the product, but given my situation and the fact that it simply does not work correctly without crashing I am having to put it on hold.
I am sure some of you will say "Well maybe it's your device drivers, or it's a plugin or it's this or that. But the thing for me is using REAPER doesn't have that problem, Why does Sonar ya know...... Perhaps Sonar could take a little different approach in the future to resolve these problems before they are problems. I mean, if a plugin is the problem : "Crash the plugin, have a fault report" but don't crash the entire DAW and everything.
What brought me to changing DAW's? The most disturbing thing of all for me was I had spent weeks on recording a song in Sonar, because of the crashes I saved everything as a BUNDLE file and also had the Auto SAVE function on. I recorded a track and went to save my SONG as a bundle file, while doing so the entire DAW crashed and in the process of saving "Which was an overwrite because obviously if you are saving the same thing over and over you are going to click on the same file name" = "Which I know some of you will say - NO YOU WONT, But the bottom line and WHOLE POINT IS YOU SHOULD NOT HAVE TO REGARDLESS".
So the lack of technical support response, multiple crashes, loss of projects is why I will no longer be using Sonar Pro or anything else Cakewalk for the time being.
Why post this? It's an attempt to INFORM CAKEWALK of my issues as a customer. Sure I could call them and wait on the phone forever. But I'm not going to do that, I shouldn't have to considering all the crash fault reports I have sent, somewhere in the neighborhood of 40 or so or more.
Either way. NO, it's not my fault, it's not Windows 10's fault, it's not my devices fault, it's not my plugins fault, because every demo of every other DAW I have tried they work in fine. As for me, I am switching to Reaper for now and hopefully Cakewalk will change it's BUG FIXES policy to include those of us who did not buy the lifetime updates. Say what you want, but I purchased a product in my case that was sold to me as "IN WORKING ORDER AND COMPATIBLE", I didn't purchase "Or so I thought" a program that "Works until you try and use it".
If nothing else, Cakewalk should own up and start a list of incompatible plugins. I'm sure some of you will say "No it's not cakewalk's fault because those drivers and those plugins should be compatible!"..... Well I got news for you : "THEY ARE like I said in every OTHER daw that I have demoed and working 100% fine WITHOUT CRASHES IN REAPER FOR ME NOW". So no, it is NOT MY fault and I am sick and tired of having the buck/blame passed to me as a consumer in this situation after purchasing.
Whatever the case, FLAME AWAY, DON'T FEAR THE REAPER is about all I got to say about that...............
I bid you adieu!