April 27, 2022 – The Cubase 12.0.20 maintenance update is now available. The update introduces some improvements to the new MIDI Remote integration and also a lot of fixes and enhancements in other areas of the application.
If you are still experiencing performance issues after the installation of Cubase 12.0.20, please let us know here: Cubase 12.0.20 performance issues - #2
Thanks for this update! Huge difference on my both Windows and Mac systems - earlier the asio performance meter was really unstable even with an empty project.
Macbook M1 Pro 16", 32gb ram, late2021, OSX Monterey
PC i7-6800K, Win 10, 32gb Ram, RME fireface 400
Earlier it was quite unstable at 512 buffer, but much worse at 128. Now looks stable on both
Cheers
Since the v12 I have always the same problem with an interminable scan of the VST3 and I’m not the only one who have that issue … Last elapsed time of start Cubase : 6 minutes 30 before to have the hub appears !!! and with the v12.0.20 … it’s a nightmare really ! I have opened a ticket with Steinberg but nothing for the moment I have x times deleted my preferences etc … I hope they will have other idea to save my situation …
Gigabyte Z390 Designare i9 9900K with 32 Gb RAM and all on SSD for the data we can’t say it’s a little machine which have no cpu power !!!
I had another issue which was close cubase = freeze and I was able to solve it by change the launch of cubase by mode administrator, now Cubase closes properly
Suddenly Cubase 12 started to hang on startup today. It have worked flawless since I installed it. I feel like there is an issue with the licenshub or something like that. I also installed the update to 12.0.20. Same thing happens! Could not have been a worse time this happend. And I just got my self a new Moog today I want to make music.
EDIT: The same issue is with Cubase 11. Also hangs on startup.
I had the same thing happen to me earlier, not had an issue with Cubase starting up in the past - but with 12.0.20, second time I went to use it - it just refused to start, even in safe mode.
Restarted my machine and it was fixed - so make sure you try that. In my case I think something had just locked up in the background I guess.