aspenleaf
My problems with X2a have mostly been from crashes...I have a state of the art computer and everything is updated.
Unfortunately, as I have found out through hard experience, a state of the art computer isn't always the answer. In particular, I've found graphics cards and drivers to be huge sources of problems both in terms of reliability and crashes. This has affected Sonar but also some (but not all) other programs (I won't name names, don't want to look like I'm dissing competitors). Finding the right graphics card solved the problems with all affected programs.
On the Mac, I had a series of incredibly vexing, random crashes but only with certain programs and on certain files. Eventually I re-installed the operating system and it seemed okay for a while, but the random crashes continued. I tried checking RAM and it was fine. But then I checked RAM with MemTest, which runs from the Mac's CLI and loads from a custom disk so it doesn't use the Mac's RAM...it located a bad memory stick. Once I fixed that, the problems were solved.
I, and many other people, have used X2 without major problems but just the occasional "I don't know what happened but I restarted it and it seems to be working now"-type stuff. The problems you're describing sound major and (I would assume) caused by some interaction between X2 and your system. Granted, it would be nice if Cakewalk could make a program so bulletproof system interactions wouldn't influence it, but we all know that's not possible...one can only hope it's as bulletproof as possible with as many systems as possible.
The easiest way to find out if the X2 problems you've experienced with your system carry over to X3 is to set a system restore point, download and install the X3 demo, then barrage it with the things you do that cause crashes. Then uninstall and depending on the results of your tests, keep it uninstalled, or upgrade.
I'm just being frank about your chances of Cakewalk fixing all of the issues for free before moving on to another paid upgrade.
I can guarantee that Cakewalk will NEVER fix all of the issues because fixing issues can often cause other issues. The workaround for the POD Farm and UA plug-ins are prime examples, but there are more subtle ones.
The analogy I use is releasing records. You can mix a record for decades and find increasingly fine points you want to tweak. But past a certain point, you just have to say "This record is done" and start work on the next one. Well, unless you're Tom Scholz, of course