If Steinberg has been deleting threads, that would be a reversal of a positive trend recently. They seem to have become much more level-headed recently, so this would indeed be unwelcome news. I'll assume the best for now, and it was either a moved thread or a mistake on some moderator's part.
But what's more unwelcome is the stream of issues that this 7.0 release carries with it... at least much more than the last major release as far as I can tell from the Steinberg forum. I've decided to wait this one out even longer than I first mentioned... at least until the first fully-supported maintenance release, and even then I'll decide if I want to wait one more maintenance release. I can't afford any downtime and I'm not interested in frustrating beta-testing.
What is really starting to bug me is that Steinberg/Yamaha's own hardware has issues with C7. This is really unwelcome news. I currently only have a CC121 (which is supposedly working okay with C7, but with a few minor issues), but I used to have an MR816 and other Yamaha hardware (including the N12) -- all great products -- but it's perplexing to me how Steinberg/Yamaha dropped the ball on compatibility with their own gear! The list of complaints on their own hardware is disturbing, and frankly unacceptable! It should work flawlessly out of the gate! What the heck is going on over there?
These and other reported and admitted C7 issues do concern me, and I'm just hoping that this isn't a reversal of a good trend on Steinberg's part... I'll cut them some slack this round so they can get this release fixed in the next few months, but I hope this doesn't mean we're going back to the "old" Steinberg. The "old" Steinberg drove me away from Cubase for a few years and I don't think I'd like another dose of that.
But it's clear to me now that just based on their own hardware compatibility alone, Steinberg should have waited another couple of months to release C7.
And if they've botched the performance of the engine and jumped the gun due to their ambition with ASIO Guard too, I don't know what I'll think. They need to get this ironed out quickly, openly, and professionally.
BUT, I repeat we really don't know the story yet about the true situation with ASIO Guard. We need someone to do a reputable, definitive, honest, technically savvy, side-by-side DAWbench comparison with C6.5 to show the actual numbers! ( I'm looking at you, Vin!
) Until that's done, we can't really accept anecdotal, non-scientific commentary or opinion of forum users as evidence that Steinberg screwed up on ASIO Guard. For all we know, there could have been a dozen other apps/plugins/drivers/etc., that those critics also upgraded at the same time they installed C7 that could be causing performance issues. A REAL test, by someone who knows what they are doing still needs to be done!
I'd volunteer myself, but I don't have the time right now, nor can I afford any issues with my main Cubase DAW. I have to sit here on 6.5 until the dust settles. Some other brave soul will have to do the dirty work on C7. But until some trusted, confirmed DAWbench test results come in, it's pointless for us to speculate based on such shoddy anecdotal information coming out of the Steinberg forum.
In any case, I've come to the belief that Steinberg simply jumped the gun on this release. It's a couple months shy of deserving a non-beta label. Only time will tell if this is a bump in the road, or something more problematic at Steinberg HQ.
I'll cross my fingers that it's just a bump in the road.