I love Steinberg but totally agree , this should have been sorted within hours , not MONTHS !
like others i rolled back and will not be going forward any more until updated are tried and tested to be working as reverting back to a previous version is a PITA
Be careful , it’s not all sunshine at Bitwigs either at the moment
I fully agree. A problem that bothers a lot to others that I mentioned in my peers. We don’t have a forecast of updates, it’s been more than 2 months and it makes me sad, because we want everything to work better. These problems had to be resolved in a short time.
I really hope I get the performance of V11 back again, (W10) - I’d really love to switch to 12but 11 is so much easier on the CPU for me, and others too…
I know how hard it can be for developers under pressure to get new features out the door so the company stays competitive with the new kids on the block.
But this situation where never a single version actually closes in on stable, usable perfection just isn’t working anymore. The entire model the whole software industry is all about now, CI/CD, nothing ever truly stabilizing, I think is inherently problematic. Don’t get me started on Agile/Scrum: we’ll be here for a while. They’re trying to address problems, but their in-practice implementation so often keeps digging up and creating new ones.
I wish somehow humanity would get past this need to disrupt, disrupt, disrupt in the spirit of innovation. I think it’s more common for traditional musicians to achieve obvious mastery of a given instrument because they are so stable: they’re not getting new shapes, weights, & features all the time.
But since we need new features, and since I’d be hypocritical here if I didn’t acknowledge my own “feature request” in the mention of Bitwig’s “modulate anything” system, I think the only way to go is to release “LTS” versions like Ubuntu does, for example, that are meant to veer towards perfection and engineering resources are devoted to just that: squashing bugs and optimizing performance–that are developed for years with this sole purpose in mind.
I mean, really: can you imagine if, in three years, we were to end up with an absolutely dead-stable, highly performant Cubase 12 with almost no bugs left? How awesome would that be? How many of us would feel compelled to get Cubase 15 or whatever the latest version Dom Sigales is losing his effervescent mind over on YouTube? I’m sure some of us would, and I’d even install it in parallel out of curiosity, perhaps.
But some days, I just wanna get some bloody music done, y’know?
Thank you for this comment, this is describing the problem exactly as it is. If you like starting a rant about Agile and Scrum let me know, I will join you immediately.
You are absolutely right.
I keep reporting issues/bugs and at this point I have about 15-20 bug reports open at Steinberg Support, which are confirmed as well (they added their internal ticket codes to the title). They are managed by another (new?) support member since a moth or two, and the latest reports have been handled very quickly, so I am optimistic, that these are fixed faster than in the past (hopefully).
Bug fixes and removing inconsistencies are more important than new features imho, even if its hard for me to say that…
My top FRs are Tabbed Plugin Windows, Gapless Audio engine, Sandboxing and Clip gain, and I really really hope they make it into the program soon, but first its needed to sort out the problems. 
The problem ist that “stable” (as in feature-stable) doesn’t sell. What sells is new features, because that is what probably a majority of users is asking for.
I agree though that often in the software business it is “innovation for innovation’s sake”, which often means just following the latest fad in UI design (like all the dark GUIs that kept cropping up in the recent years).
That is not a bad idea. Another option would be to have a public beta phase for new major releases, which could especially help catch the edge cases and problems with specific system configurations. Anyone who is willing to install the beta is aware of the risks.
The marketing department would probably have objections, since they cannot have a traditional “surprise” launch day praising all the new features, but that could be outweighed by the beta testers spreading cool features by word of mouth.
It is a bit more organisation coordinating the beta tests and bug reports, of course.
It could also strengthen the community aspect and make users feel more involved.
I recommend something like this 
:
Also have this issue, has been present since the initial launch of 12 as far as I know - glad im not the only one.
M1 Mac Mini Gen 1.
In the defence of Cubase, they are trying to implement a new native CPU architecture as well as land a new authentication system. I have a strong hope we will see these solved in time.
This is true.
If you have to rely on a system, because of your work and you earn your money with it and cannot afford any downtime, then don’t jump to a completely new architecture before you know for sure it will work.
Wait until it is tried and tested and then switch.
С11 works smooth and fine on Apple Silicon CPU’s, such as it works fine and smooth on Intel machines
Not for everyone apparently. 
If you look through the threads, most of them are from mac users, having performance issues, and quite a lot use the M1 chip already.
And I am not talking about Cubase only, but about 3rd party plugins as well.
C11 is running in Rosetta Mode, because it is pure Intel Code, not Silicon.
While totally true, at the same time, as consumers it’s important to demand a good product thats released to a certain standard. All im trying to say is, for the time being im happy to give Steinberg a bit of a break but I do hope we reach a fundamental level of fantastic performance before the next .5 update as we shouldn’t be paying for software which doesn’t work as expected.
Yep, agree.
Btw. AFAIK there is no 0.5 update planned anymore
Ahhh, interesting I didn’t know that - thanks for letting me know.
In my workflow C12 is running in Rosetta as well. And it’s awful
I have absolutely the same issues in C12 on M1 and Intel Macs, and I don’t have them with C11
Are some 3rd party plugins preventing you to switch to native?
Yes, still have some
But in native Silicon mode C12 is the same bad