The Cakewalk folks are in a no-win situation.
When they release something too soon, and it has bugs, folks here in the forum bash them incessantly over that.
If they instead take the time to either add complex new functionality, OR they take time to do more testing to reduce the insertion of additional bugs, then folks in the forum freak out and bash them incessantly over that.
It's almost like they are in the position of being referees, in that they are GUARANTEED that a whole bunch of folks are going to be dissatisfied with any call they make.
And, has been pointed out before, for a GOOD many years, this cycle has been repeating itself, so wise up folks, it is likely how it will remain. They are OBVIOUSLY deep in the middle of whatever they are working on, and whenever they feel like they have the set of things that will make their internal deadlines, as well as honoring any partnership contractual timelines and restrictions, at THAT point they will have the collection of items that will constitute the next release of their software.
They have clearly pointed out an awareness of everybody's feelings on all of this, and they will at the same time do what they do, in THEIR time frame, with THEIR collection of items to be included in the release.
So, GET OVER IT, or don't.
If the step sequencer feature request I submitted long ago keeps getting bumped because they choose to work on things like Pro Channel, or Take Lanes, or any number of features that affect WAY more folks than me, I support that, because it makes good business sense for them to do that. Do I still hope that someday that change will filter into a release? Sure, I do. But I am quite happy that Pro Channel exists instead of them providing a small alteration to something that is really only an annoyance for me.
I want them to fix show stoppers above all else. I believe they have a pretty good track record of doing just that. We saw that with the multiple sub-releases for X1, and we saw a quick fix come out to deal with show stoppers when X2 first appeared.
A lot of the bugs that are out there are more annoyances than anything, and I am sure that as they have ALWAYS prioritized their work efforts for the past 20 years or so, that they are continuing to address things that they feel affect the most folks beneficially - fixing the things that are MOST annoying or truly are real problems where there are no work arounds. As I noted before, the X2a release fixed more than 250 bugs, in addition to adding new functionality and cleaning some things up a bit.
Lastly, time and time again, in the course of the countless hours I spend trying to help folks to the best of my ability, I see a large percentage of the issues out there from inexperience, not reading installation instructions, obsolete hardware that is long past when it should have been expected to work with newer operating systems and DAW software - where drivers are years and years old - and yet folks think that it is Cakewalk's fault, or people have issues caused many times by mostly older 32-bit plugins (and some 64-bit ones too, but mostly 32-bit ones) running on 64-bit systems. I believe that there are lots of folks about there who have X2a installed and working fine with 32-bit plugins ON 32-BIT WINDOWS.
I have Native Instruments software that just will NOT run in Windows 8, and may not have run in Windows 7 (can't remember). I LOVED their Pro-53 software, but it just does NOT work anymore on current OS versions. If I REALLY needed to hang on to it, I could build a machine that runs XP Pro or Windows 7 (if it still worked there, again cannot remember), and it would work just fine. Instead, I have chosen to have MY system run 64-bit Windows 8, with 64-bit Sonar X2a, and ONLY 64-bit plugins, with the exception of the MinimogueVA and the ARP2600VA, which I love dearly - and they happen to work just fine. And guess what? I NEVER have had a crash with Sonar X2a.
Bottom line, there ARE configurations that run crash free, and there are known things that can cause problems. We have choices that we have made and continue to make, and those choices affect the stability of the systems we are trying to work with. When things CAN be adjusted or worked around, COOL, make the changes and keep on trucking.
WE make the choices as to how we set things up, and WE have to live with the consequences, both good and bad. That's life. THEY will continue to do their best at developing a balance of new features, enhancing existing features, and trying to eliminate bugs in a top-down prioritization, releasing each version of their product when it meets THEIR corporate planning and delivery schedule needs.
The end.
Bob Bone