They had two months between the bug report and the build date, and the virtual keyboard onscreen display still does not light keys when you press them.
I’m -very- close to being done with Cubase. Studio One v4 came out today, and their chord track is miles better than Cubase’s (it actually works on audio, not just MIDI, if I didn’t hallucinate whilst watching the launch livestream). They already have the equivalent of offline processing and a better UI. They have ARA (and now ARA2, as of today) for use with Melodyne (which will accomodate the chord track manipulation inside S1).
As of today, there are fewer and fewer reasons to stick with Cubase. The things I would have hesitated over are largely addressed elsewhere. The only one holding me back right now is that Komplete Kontrol has DAW integration for Cubase but not S1 right now, and I have an S61 arriving next month.
Given Cubase’s QA lately, and lack of an expedient fix to a simple-but-important issue, I’m very close to jumping ship, or at least making S1 my main DAW once I’m up to speed at least as far as I’m into Cubase. If I didn’t mind the migration from FL Studio to Cubase, you can bet that the nearly-identical workflow from Cubase to Studio One will not phase me in the slightest.
Let’s get with the program, -fix- 9.5 in the next maintenance release, and actually give us things we need for 10. Things like ARA2 would be a hell of a start at redemption. Considering the build date on the update is three weeks ago, you’d think someone in testing and/or QA would have ‘discovered’ that the virtual keyboard wasn’t fixed, even though I know there to be an open ticket. Funny how this wasn’t caught during the ‘testing’ period. (Presumably that’s the reason for the delay between build date and release.)
Miffed does not even begin to describe my mood right now.
Shape up, or lose a customer (and as many as I hold sway over). I know I have brought people to Cubase via recommendations; I can just as easily steer them elsewhere.