Noel Borthwick [Cakewalk]
julianochrisway
So forget conspiracy theories. Cakewalk is closed for Gibson's problems and not on account of bugs. If bugs were something that prevented DAW sales, ProTools wouldn't even sell. Because in every project I do, I have bugs, very different from the Platinum Sonar. My latest project is a 28 track single with many plugins and samples on KONTATK.
So that's it, I made this text about my vision of what happened to the company, putting facts on the table, without creating crazy theories.
Hi Julian thanks for your rational discussion. Yeah the shutdown of Cakewalk was mainly to do with Gibson's focus change and of course our Company's profitability. It had zero to do with problems with the actual product. The evolution of SONAR was at its highest peak ever and we had some really amazing features and even more to come so its bittersweet that this happened at the peak. Regarding bugs, ALL software products have bugs and kid yourself not ALL the DAW's have similar or worse issues depending on where you look and how you use the software.
Bugs are a whole topic in itself that I may write a blog about. Some end users think that companies ignore bugs intentionally in favor of quick profits and shiny features. Nothing could be further from the truth. The main reason bugs exist are because there are some enormously complex and difficult to reproduce scenarios that prevent them being found by developers. We had certain bugs that only showed up for a tiny set of users on their systems only when using myriads of plugins. In such scenarios the time cost of identifying and fixing those bugs becomes huge (it can take a developer or qa team, weeks to even get to the problem let alone fix it). So its common for software companies prioritize more common bugs that affect a greater number of users in normal use. We certainly had our share of esoteric bugs, but by far we made tremendous strides over the last couple of years with the agile monthly update model to eradicate most of the most frequently reported issues. Our bug tracking metrics definitely show this.
I recommend that folks take a wait and see approach over the next few months. It takes time to transition a company to a new owner. The product works great today and will continue to do so for many years even if there were no changes. There is no pressing need to immediately stop work on SONAR and jump to a different product despite other companies bids to acquire Cakewalk customers. I'd personally like to see our customers support a company that actually wants to retain the heritage of this great product and build upon it.
The trouble with that advice Noel is that it doesn't give anyone any more information by which they can make a rational decision on whether or not to go with a new DAW. People are naturally worried that if for some reason they have to reinstall Sonar in the future, it might happen at a time after which the reactivation servers have been shut down. Ultimately the nightmare scenario would be not being able to load projects and losing work. It doesn't matter how much we're reassured that this will never happen, or how much we're assured that we'll receive some kind of offline key, I think everyone's aware that the current situation is one in which anything could happen at any minute on the whim of Gibson.
Your last paragraph is certainly interesting and is going to get a lot of people talking. Does Noel know something? Is there something on the cards? Are there potential buyers? Are talks taking place as we speak? However without something more definite, people are stuck with the possibility that Sonar might remain unsupported in perpetuity, and while crossgrade offers are still on the cards then people are going to continue to jump ship.
Regarding bugs, I cannot shake off my hunch that something really weird happens to Sonar projects the older and larger they get. And this did not make bug hunting easy. As an example, not so long ago I tried to record a soft synth performance in which I had 10 or so synth parameters mapped to my controller and I write enabled the synth. The controls worked during the performance, and I saw all envelopes being drawn on screen as I adjusted them. However, when I hit stop, some of the envelopes were missing. They weren't on screen and they weren't in the edit filter list. Not only that, but envelopes for parameters I hadn't gone anywhere near seemed to have taken their place. Deleting one of those caused another envelope to disappear at the same time. And then other weird stuff would happen as I was adding or removing automation lanes. It got to a point where I could not describe what was happening because it was so illogical. And it wasn't the first time this had happened to me (a variety of synths). So then you go to create a bug report and find you cannot reproduce anything to a recipe. You try to recreate in a new project, but of course everything seems to work just fine in a fresh project. Sometimes trying to figure out recipes in a large project is really time consuming, because you end up having to close and relaunch the project multiple times to try different stuff, and when the project takes a minute or two to load, that's a very slow process. So sometimes I spent entire evenings like this looking for an "aha" moment only to come up with nothing. Along with the VST setting reset bug which has caused me to lose countless hours of work, I got to the point where I started to think these bugs were going to be baked into the program forever. And when Cakewalk was shut down that feeling just blossomed.
I appreciate your point that all DAW's have bugs. I'm not sure if they're all equally as serious though. For example, before Sonar I used Pro Tools, and apart from CPU/memory performance issues due to the fact that it was only 32 bit and I was trying to run a lot of synths and sample libraries, I had some pretty large scale projects going in it and not once did I ever encounter anything serious regarding things like editing/automation/plugin settings. Nothing weird creeping into the project as it got bigger. Nothing that caused me to lose work. That whole meat and potatoes side of the program was rock solid for me. I switched to Sonar because it was 64-bit and I preferred the workflow. But in terms of encountering bugs and weirdness, it has been a lot more problematic than Pro Tools in that respect.