microapp
Anderton
The only drawback I've found is that SONAR is very picky about its Windows environment. Its code has hooks deep into the operating system, which is one reason why a Mac version will probably never appear (although of course, it runs great under Boot Camp). To SONAR, a Windows computer is like a combination lock - when all the tumblers are in place, it opens up. But that's why this forum is so great - because odds are someone has experienced whatever problem you have, and can offer a solution or a workaround.
There's a reason why this forum is considered one of SONAR's outstanding "features"!
Craig,
You make it sound like Sonar's pickyness is a feature.
Not sure how you got that out of his post. The one thing I like about Craig being involved with Gibson and thus indirectly with Cakewalk is that he's pretty blunt about it's shortcomings and the stability weirdness is one that I've seen him acknowledge on multiple occasions (which I think he has done again here).
It's not that it's so buggy that it's unuseable but you have to be a little more careful with it than with a couple of the other DAWs out there (and really I think there are only two or three that outperform in this regard so it's not like Sonar is trailing the pack by any means... it's just not currently at the very top of the stability list). What I have noticed in the past year is a massive improvement in stability and concerted effort to resolve these issues. Having someone like Craig around who knows what the heck he's talking about and is willing to point out these things will inevitably benefit the end product much more than a yes man only concerned with marketing cliches and moving product.
The other thing is with X1 and X2 you were dealing with a HUGE pile of new stuff... actually almost a whole new program really with X1. As far as X2 I think a major problem was that on top of being only the second release after such a massive rewrite they started implementing some really nutty stuff which may have been poorly timed.
Like coding it for Windows 8 before Win 8 was even released and cramming in a ton of touch features. I'm guessing that they wrote it based on whatever pre-release MS gives to developers and then when 8 finally did come out MS had changed so much crap it turned into a mess (and then MS continued screwing around with 8 quite drastically because it was turning into yet another "between good versions" flop like Vista or ME and the like). The Bakers probably just threw their hands up in the air and said "Frack it! This is a mess. let's just focus on getting the next version right." and they did. They had a semi mature and patched Win 8 to program around, touch had advanced and become less of a joke and Sonar X series itself had had enough time to be user tested on a broader level so a lot of those nasty quirks could be ironed out.
Now they have a good, solid and mature platform to work with instead of chasing around a million little bugs and oddities. They can take their time to really hammer out some of the remaining little program farts and implement all the crazy requests we users are making (and it is already starting to show with this current release).
I mean look at the release of X3 compared to X2. There was very little squawking with X3 and most of the problems were relatively minor and most got patched pretty quickly. Now with the "New" Sonar (still wish there was a more definitive name for it than that but whatever) we've seen a few complaints here and there but overall they seem even less than with X3 and we are still in the absolute raw first release (as in no patches to date).
Perhaps I'm being overly optimistic but I think things are going in the right direction as far as stability and I think they have a good chance of getting rid of that "buggy" reputation once and for all and may even get themselves right at the top of the list of DAWs in this regard. There is ONE contender I think they will have a VERY hard time over taking in regards to stability and accessibility on low powered systems (who shall remain nameless) but the robustness of the package and hyper advanced workflow compared to that competitor kind of makes it moot IMO.
Anyway... I've never seen Craig make excuses for bugs or shortfalls. Quite the opposite in fact.
As far as assuming the OP was a troll... well I may have jump the gun a little but really that post served no purpose. If they return with some legitimate details and desire to solve the problems I will immediately apologize. Considering they marked my first post as "Best Answer" though gives me the impression I did not really offend them.
Who knows... it's the internet. Wackiness abounds.