I have all the sympathy for the team, it’s very clear you had a lot on your hands, with new features, architectural changes like the MIDI Remote and the whole licensing thing.
Still, the image that comes across is the one that I mentioned above.
I’m a Nuendo user for some time but I did install a Cubase 12 AI license I had.
After trying it on the same workstation on which Nuendo 11.0.41 runs fine, I became very certain that I will not upgrade to Nuendo 12 anytime soon. Freezes on start, graphic glitches, crashes on exit etc.
It’s all catch 22 with this stuff. Find me the posts where users are saying, “it’s not okay BUT I still have Cubase 11 so I will use that for now, take your time with 12.0.20, take a few months, get it perfect, then roll it out”.
Those posts are few and far between, most everyone is saying, “it’s broken, where is the fix? Is anyone doing anything about this?”
And those same ppl will complain 12.0.20 was rushed if it doesn’t fix their exact issue. Everyone screams for software and complains the vendor is way too slow until they get it. Then if it doesn’t work on their system, they complain they never wanted it that quick lol.
Of course I’m not saying this about any particular person here, it’s a general feel I get from reading posts prior to C12 release and now.
It will be the same with M1 users waiting for Pro Tools. They are all thinking why is Avid sooOOoooo slow to develop this. If it does not work properly on their system when it’s released they will say it’s rushed.
If we all had the same OS, CPU, motherboard, chipset, audio drivers, plugins. We could complain and say this was not tested. But everyone’s system is almost unique. This is the internet, ppl come here to complain, and so they should. They have a right to. But there are lots of ppl who have C12 working very well right now. So this is not a good straw pole of issues with C12.
Of course if your one of the unfortunate ppl who are having a bad time of it I feel for you. It’s horrid when it happens. I have complained a lot when it’s been me so I get it.
Well, there’s no doubt that perception matters quite a bit.
Our perception here is that Cubase 12 Pro is a robust and reliable product which performs at least as well as C11.
It doesn’t freeze or crash, either during start, operation or shutdown and, other than the recent plugin window sizing problem, doesn’t exhibit any graphic anomalies that we have experienced.
We run Cubase synced with Nuendo (on separate W10 machines) and we’re looking forward to the Nuendo 12 release so that we can begin testing. If it goes as well as C12, it will be in production once the current project is complete.
I’m not downplaying anyone else’s problems, but they’re not universal and, as Matthias has just said, it’s not that simple.
Yes many performances problems… especially with vst effects and instruments.
Sometimes the performance bar get red with noisy interruptions
Back to PRO11
That’s good to know. Is there an anticipated release date?
Perhaps there is a lesson to be learned here? Testing on your own machines is not that effective. Microsoft recruited users to test beta releases beginning with windows 8. Real world (AKA Wild West) testing is needed.
I am a former software and database designer, developer, and test engineer for regulated medical devices and systems.
I’m fairly sure that is exactly how they do test. It’s not a free for all but there are beta testers selected who are users as well. It’s just not open to everyone like Ableton.
They have been making Cubase for over 30 years now. Every company has a problem with a release at some point and testing it for longer might/might not catch it.
It could be a number of things from a plug-ins causing issues to a windows update to old CPU chipsets. Controller software causing issues.
It might also be that, as there is noise on here about an issue with C12, that other issues with plugins are not investigated as much. Really everyone should move all of their plugins out of every dll folder that Cubase looks at, Then test it with only stock plugins loaded into the program, not project, actual C12. Then put those plugins and instruments back 10 at a time. Restart and test Cubase, then put the next 20 back in. See if any of those batches cause issues. I bet a lot of users have done that and found it’s the base C12 platform that’s the issue. But for others they might not have tested that yet and they could have one plugin causing mayhem.
I could not do anything with Pro Tools on my M1 Mac under Rosetta, it just kept crashing, I removed every plugin and then put them back in batches. Only to find it was a compressor I bought ages ago that caused the issue. Pro Tools hung on waves plugins but this plugin was totally different. Moved it out and everything worked.
Even now there is one waves plug-in that crashes Ableton every time. Also a Rob Papen delay that causes C12 to sometimes crash.
Sometimes it is as simple as throwing more ppl at it. It’s worth remembering that lots of ppl on windows have no issues what-so-ever and we do not know the percentage that do have issues.
@Ronkay,
Are you on Windows? Did you try running Cubase as Administrator? For me that solved exactly this problem. I know it’s a workaround but worth the try.
We all realize that when dealing with updates from both Steinberg and Windows, etc you will always have some problems but like I stated before we’re just asking that we be able to open and close our program. This is something that must be worked out before releasing any computer program. The other more mundane or serious problems, that may happen along the way, can be handled as they come. It would be like being a luxury car salesman but can’t even get the car to turn off after demonstrating it to a new potential customer. Even worse, what if it won’t even start or gives you an error sign in the car that your customer sees. You will not sell or demo that car again until it is reasonably or 100% functional.