i think CW didn't help by taking a stable programme (8.5) and then producing X1 - not only was it a bit wonky, but of course there was the total redesign. I think if at THAT point they had overhauled the audio engine/VST3 as for X3, then there would have been pain for one release, rather than 2 consecutive ones. I'm sure hands were tied by Roland though. Then the almost radio-silence through X2 on these forums really cheesed a lot of people off.
 
I use X2 (not often these days...kids=no time!) and it's pretty stable for me, but then I don't do much advanced MIDI work, and I got it not far before X3 was coming out, on sale, so I knew at that point there wouldn't be any further development.  Likewise, I will probably get X3 next August time.
 
I hope they do stay afloat and the Gibson tie-in is successful, and like everyone says, ALL software companies have these moments at times; Logic going Mac only, Cubase going SX then dropping SX etc.

Just to throw a "reality" check into the mix... here is the last thread I posted with X2. Even when I read that again I can recall very distinctly how irate I was when I wrote it, yet it flows enough to help other forum members...
 
I had a bug with no work around at all... X2 was 100% unreliable, gave me a "phantom" to chase (while my patience lasted), and did have me step away from any DAW for months (I in fact use no other, so X2 stopped all music recording in its tracks). I would even joke when I played by flipping on my amp and saying "Check this out..." when plugging in my guitar. During those days, I didn't even fall back on X1d.... I simply played, and it gave me a time window to do other things... like "truly" rebuild a guitar I had put off for years... so blessings come disguised at times...
 
Then along came X3... by that time, I had X2a online, stable, and working... but my experience with X2 made my confidence level at an "all time low"... yet not once did I come in and "generally bash X2," which is probably more to my real point here...
 
X3 gave me an astound appreciation for this forum (CW's "ultimate asset," in my opinion), its members, and how willing people are to help others... which is GREAT. I remember when I had my first post marked as helpful... I told a friend and they asked why I cared so much... and my reply was "Because I have been a leech there, only going when I need something, and am finally giving back!"
 
(All of) that said... when a user has a problem, I see everyone here try to help... when a user comes in without a definitive issue, people ask to clarify, offer suggestions, and come to better solutions/work arounds... "perfect"
 
When someone comes in to perform "general bashing" without a specific issue, etc., it is very difficult to give solutions... and when it becomes apparent that their "only" purpose is such, it is even more difficult to help...
 
When it comes to "general bashing" I can bring a 14lb post maul into the fray, especially regarding X2... and rarely do I swing it.... yet, here I am supporting X3. I can offer advice from my experience, but can do no more than that.
 
Could I participate on a "general bashing" on X2... yup... more than anyone else (I think)... would I?? hell no... this is what turns my stomach...

I can sure relate to problems with Sonar. X1 was an absolute nightmare for me. Until X1C I couldn't even get it to load.
While I got sympathy from many of the forum old timers I also copped heaps of negative feedback in response to my complaints. I was even accused of lying at one stage and being a serial pest or some such.

That was when I learned that inexplicable incompatibilities do occur between different versions of the same software on the same hardware. This same computer ran 8.5.3 perfectly well, sucked until X1C came out and has been fine since even X2a is pretty good with no deal breakers. X3 has been a gem all the way.

Living in the land of oz, phone support isn't really practical and I've got to admit that email support leaves a lot to be desired. At that time I did move to a different daw until Sonar was sorted out. Since then I've used what works and live firmly in the real world where I accept that all software has problems, I don't like it and agree with Danny when he was playing devils advocate about how we are forced to accepting things about software that just aren't tolerated in other commercial areas. Yet I confess I don't have an answer.

I do know that this forum has once again become a useful resource again, many of the oldies have returned those that never left are positive again and there's this spirit of cooperation in general that is great to be part of.

Complaint as means of venting, to get it off your chest is fine, just say that's what it is. Stating problems and asking for help is what this forum is best at and above all, take responsibility for your own education about your software and the many resources at your disposal. Constant complaining about the unchangeable seems pointless, if it's that bad use something else and make music, after all it's all about the music isn't it?

Anyway that's my 2 bobs worth!

I believe that Cakewalk also would like to get out from under all the X2 bugs and problems.
 
In saying that, maybe with the small problems in X3 that will probably be fixed in X3d will have put them on track as far as the learning curve goes and know exactly how to fix X2 in a fast update. They will not spend all their time on X2 , but to satisfy X2 customere a little I think they will try to do something.
 
At least that is the way I think about it.
 
 

I find quite a lot of disrespect for people that have problems with Sonar on this forum.  Sort of a love it or leave it mentality.
 
It's not disrespect, if people want to jump ship - jump. We're here to help when we can, discussions can be interesting as well within the product as long as they are specific or within expectations. Otherwise it's a waste of our time.
 
I regard Cakewalk now as two different companies, the pre X-3 company and the current X-3 company. The time around X-2 esp sucked, X-3 company is looking good and has learnt or is learning from its mistakes. If people have had enough of their Sonar version, come into X-3 land, or jump ship (whatever). Just not interested in debating about it whatsoever. You are either in or you are out.
 
Cheers...

in this forum you have to explicitly:

1. say how much you love sonar
2. update your sig
3. not use asio4all
4. not use free VSTs
5. defrag you hard drive
6. use some third party driver checker
7. update windoze

then someone might try & reproduce your issue :)

The most important thing for software is that it works. All else is meaningless if the program you are using is unstable. Crashing is not something we as users should become accustom to.  It shouldn't matter who is developing it or how much we may like the developers. Instability should never be viewed as part and parcel of using software. 
 
True bugs will be found in just about any software out there. That does not mean that its OK to produce a product that will not run without crashing at very inopportune times. BTW all crashing is inopportune.
 
Its also important to note whether its really the software that is causing instability. We need to be very careful in pointing fingers at what may turn out to be wrong culprits.
 
Before we make a claim about instability we need to be very sure that it is in fact the software that is the problem. One clue that this may be the case is that others don't have the same problems even though they are doing the same things. 
 
When a poster sets up a recipe for finding a bug I find it very useful if others can replicate the same action. 
 
We also need to distinguish true bugs from poster dislike or a different way of doing things that the poster may not know about.
 
None the less none of us should be required to live with unstable software.  
 

lawp
in this forum you have to explicitly:

1. say how much you love sonar
2. update your sig
3. not use asio4all
4. not use free VSTs
5. defrag you hard drive
6. use some third party driver checker
7. update windoze

then someone might try & reproduce your issue :)

That is something of a generalisation (understatement).  I don't think I have ever asked/done any of the things you list.
 
I have, on the other hand, spent many hours attempting to reproduce issues that people have come across, or helping them sort it out when it is pilot error (a common event).  I am far from alone in this.
 
If your post was directed at one person, which it appeared to be, then please have the balls to address them personally, and not hurl monkey poo at everyone around you.
 
Thank you.
 
 

John
The most important thing for software is that it works. All else is meaningless if the program you are using is unstable. Crashing is not something we as users should become accustom to.  It shouldn't matter who is developing it or how much we may like the developers. Instability should never be viewed as part and parcel of using software. 
 
True bugs will be found in just about any software out there. That does not mean that its OK to produce a product that will not run without crashing at very inopportune times. BTW all crashing is inopportune.
 
Its also important to note whether its really the software that is causing instability. We need to be very careful in pointing fingers at what may turn out to be wrong culprits.
 
Before we make a claim about instability we need to be very sure that it is in fact the software that is the problem. One clue that this may be the case is that others don't have the same problems even though they are doing the same things. 
 
When a poster sets up a recipe for finding a bug I find it very useful if others can replicate the same action. 
 
We also need to distinguish true bugs from poster dislike or a different way of doing things that the poster may not know about.
 
None the less none of us should be required to live with unstable software.  
 

Well said, John, as usual.

lawp
in this forum you have to explicitly:

1. say how much you love sonar
2. update your sig
3. not use asio4all
4. not use free VSTs
5. defrag you hard drive
6. use some third party driver checker
7. update windoze

then someone might try & reproduce your issue :)

* Update your sound interface driver
* Run chkdsk
* Run sfc /scannow
* Run dism /online /cleanup-image /restorehealth
* Update your firmware everywhere.
* Use dependency Monitor
* Use process monitor
* Use file monitor
* Use latency monitor
* Configure your antivirus to exclude certain folders.
* Configure task scheduler correctly.
* Spend some time on your system doing boring stuff (not be impatient).
* Stand on one leg.
* Drink beer.
* Stop spending all your money on plugins.