Make absolutely sure your audio output settings are the same between the two Cubase versions. I initially configured asio4all on Cubase 12 in a slightly different way than Cubase 11 and I had audio output but it was really choppy.
(PS if you are on windows and are not using asio4all I recommend downloading and installing it)
Still the same disaster with 12.0.10, unusable. I tried on two different computers (I7 6700 HQ / 16 go DDR4 & the other Ryzen 7 1800X / 64 go DDR4). Canāt use a single instance of Analog Lab / Komplete Kontrol or others. I work with a RME BabyFace Pro. Everything is updated.
Thankz mr.roosā¦you just saved my day 
I have 2 monitors with an 125% scaling, and was so frustrated about the right click toolbar weird behaviour, and how midi lines just ājumpedā just by clicking on them in my second monitor.
I set the monitors to 100%, andā¦ātadaaaā it worked perfectly 
THANK YOU 
We now live in a culture where its release now and fix later , and rely on the end user to bug test
thatās what beta testing is for.
While i understand thereās lots of possible computer configs
it seems to me a programmer may have broken something in the source code, who knows
i mean the base code/programming of cubase could be really old with tacked on featureās/more lines of code that need to work together
Its v12 not v0 -
its not a few bugs its large amount of people ,that may rely on the software to make a living,
commutation with the customer base is a must for trust and caring
my logic is if you brought a car in a show room and they said the engine over heats but if you pull over and let it cool down it should be ok,
customers should not have test so we can try and fix the issue
but when it comes to software its ok to tolerate this
i brought the update and upgrade and it has been unusable for me. Ive not used it since
it just puts me in a bad mood out of frustration, and has eroded my passion for music
this is not a rant its been my experience ,i cant be bothered anymore
this is my view and opinion,
Lets hope for better in the future
I echo thatā¦all respect to Steinberg, but I very rarely buy a new update, I make a living from music, and sometimes I have to adhere to very strict timetables. Needless to say, bugs can be catastrophic to meā¦
Sorry you had this experience,
Sadly, no matter what the version, my experience is that on the 11th hour it all goes to hell, error codes, corrupted sessions, the lot, I just have to accept it and do the best I can with the situation, hugely frustrating, itās such an incredible program. And every update offers so much.
Lately, the Squasher, Imager and Queue Exporting have been invaluable to meā¦and there is so much more.
An extra effort by Steinberg to fix as many bugs as possible, would be a statement of loyalty to their customers who have stayed with them for decadesā¦
Totally agree with you. Luckily for me its a hobby
so its 100 times worse for you, i got the latest patch i have yet to test it will do after this bad taste has gone lol,
but fingers crossed
And i hope things get better for you, less stress to worry about
Many thanks!
I am at 11 and it seems to behave pretty well, as I said, still a few bugs especially near the end of a project where things are starting to go downhill , but I wonāt touch 12 just yetā¦Cheers!
here hoping for a bug free Cubaseā¦
Thanks for your comment, but actually, my cultural experience outside of Steinberg and Cubase is quite different: in my world (Cubase is a hobby), if a company contracts to deliver goods or services and doesnāt (or what is delivered is broken), there are consequences, not just shoulder shrugs of the āOh, wellā variety.
If head-in-the-sand avoidance of good customer communication and support is added to that, well thatās just embarrassing, and thatās a company that doesnāt last long.
In my experience full corporate accountability is the rule, not the exception. As it should be, right?
Iāve said all the things Iām going to say on this matter
anymore would just be unfair and edging towards a rant.
Iām sure Steinberg have taken note of peoples comments to rectify issues in the future,
I love the software Iām old enough to remember when Cubase came on a floppy disk but if companyās get complacent . its a down hill slope,
as said i made my point its up to Steinberg whether they take note and take it as constructive criticism only because we all love the software
pointless me adding more to this thread :]
Even with the upgrade to 12.0.10, my new Cubase 12 still hangs forever when (so my activity monitor tells me) it is trying to load vst attachments. Wherever I click when the "safe mode"window comes up, I canāt get Cubase 12 to work. I upgraded to Cubase 12 when my old version of Cubase (10.5) started having similar freezing/crashing problems a couple of weeks ago. Cubase 12 worked correctly for me a few times, then put up a window about having to open in safe mode. Since then, it has been freezing every time it starts, whichever button I tick on the safe screenā¦ Clearly, the problem is with plug-ins (eg Kontakt), because if I press the button to bypass all plug-ins, Cubase stops hanging and my compositions do come up on screen. However, because I have de-activated all plug-ins to get there, none of the music will sound! I am completely hamstrung, with no way of knowing what is wrong. I have looked all over the net under troubleshooting, and Cubase experts seem unaware that this is is a problem that threatens the whole future of Steinberg. Other DAWs do not seem to have the same problem, and I am seriously considering changing after several decades of using Cubase.
I use Kontakt sometimes and Fabfilter plugins always and had the same problem. It stopped when starting Cubase as Admin. Maybe worth a try if you didnāt do already. I manage to solve some other problems with Cubase 11 earlier to login as (the hidden) Admin too.
Same here. Running as admin solved a lot of problems.
A post was split to a new topic: Cubase 10.5, 11 and 12 hang on start-up
I am curious about this, how can logging in a Admin solve problems? Any problem in particular?
Many thanks!
If running as admin solves an issue it indicates underlying problem elsewhere that needs to be rectified.
By doing that youāre elevating the rights of the DAW within a user environment and it can bring more problems. For example, the ability to drag and drop files into the timeline and such like.
Itās a quick band-aid, but not recommended as a long term fix.
Thanks for clarifying, appreciated!
I am not clear how this works. But it was suggested when I was having problems with SpectraLayers. Going into the Cubase Pro .exe file, right clicking it and under ācompatibilityā checking the ārun this program as administratorā box worked for me perfectly. Why this is I have no idea.
I appreciate you letting me know.
Same for me. Once I had a problem with a Cableguys plugin in a track: Cubase hang during initializing. I logged in as Admin, run Cubase as Admin. Everything worked fine. I restarted normal, run Cubase normal and the problem was gone. This was Cubase 11. Itās still a mystery to me why.
just upgraded yesterday, and 12 is taking longer to open, longer to open files, way longer to close them (get a rotating blue ring for a long while before I can open another project), and clicking on buttons in my project feel slightly laggy compared to Cubase 11. Really frustrating. Going to read this whole thread and see if there are any tipsā¦blugh.