wst3 Do I stick with a tool I've been using for almost 20 years (how is that possible)? Do I assume the worst and move on? And where would I go?
I think this bit right here touches on why I've been so frustrated during this whole process. I think I'm not alone in this respect. Like many, I've been a loyal user of the Cakewalk/Sonar platform for more than 20 years. And it turns out, that was a mistake.
Not a mistake in the sense that I should have used something instead of Sonar. But a mistake in that I should have been using something else in addition to Sonar all along.
Cakewalk was the first software sequencer I learned. I liked it capabilities and how it functioned so I stuck with it. I saw no reason to use anything else. I learned and worked with Protools and few others while working in friends studios. But I never felt the need to install any of them on my computer or integrate any of them into my work flow. That was a mistake.
Anyone familiar with Steve Albini knows he uses analog tape almost exclusively. Not so much because of how it sounds, but in his words, because its the only medium he knows of that he can guarantee will still be accessible and workable 100 years from now.
Analog tape is not proprietary. Anyone can build a tape machine that will work with it. You can't say that about any native DAW format. All of them store their information in proprietary formats using code that they exclusively own and control. So if a DAW manufacturer closes up shop, your ability to access any work you did in that DAW will eventually go away. That's the deal with devil we all make when we decide to work in digital formats.
And there's another deal we make with the devil. Analog tape and the machines that work with it are, relatively speaking, dirt simple to use. And they all work more or less the same. So if you understand how to use one of them, you can easily use any of them. That is not the case with DAWs. Any given function on one of them can have a completely different name, workflow, and implementation on another. So moving from one to another is almost like starting from scratch again and it could take months or even years before one is able to complete projects in a new DAW without any time spent googling how to do something they've never done before or only done once a few months ago.
So what this whole Gibson/Sonar/Bandlab cluster eff has taught me is that anyone who decides to work with a DAW should in fact work with at least two DAW's and possibly three. Perhaps write/develop ideas in one, record them in another, edit/master in a third.
Because sooner or later, one of them is going to go away. You'll want to be well versed in working with something else when that happens. And you'll also want to be well versed in methods of exporting/importing projects between their proprietary formats when that happens. Working with several constantly is the only effective way to do that.