It’s here…
1 Like
I started to get stuttering and dropouts after upgrading to 14 pro. After much dicking about I found one of my vst synths to be the problem (Ascension) in this case. Removed it and no more glitching.
so now we have to remove previously working vst instruments to use cubase 14 
its been known to help on mac after an upgrade. there are several ways to replace the xml file. Doing it in Cubase should be fine. but be aware that it erases all your settings & you need to reset them back up.
for me, i currently have graphics acceleration disabled on my mac - it makes the gui a bit sluggish but i can at least work without ASIO guard drop-outs
1 Like
Ive noticed that certain presets on certain vst instruments cause horrible dropouts. Dune 3 & pigments are bad offenders, they worked ok in cubase 13 though. Also I use Ozone advanced 11 for mastering and the audio performance monitor is now regularly showing red spikes, although I dont notice any audio clicks or pops when it does, very odd. Are we now at the point where we have to disable or stop using specific plugins ? This is quite easily the worst update I have ever experienced from Steinberg, not professional at all and this was supposed to have big audio performance improvements, what a joke !
2 Likes
This exactly^^^
I installed the demo and holy Toledo…
It takes several minutes to start then decided to randomly freeze.
Every single time. Then when it does load it locks up.
Upon testing it seems that this is happening if I have any audio tracks but if there aren’t any it works which leads me to believe this has something to do w/disk drives and Cubase and/or Windows 10.
ftr, THIS DIDN’T HAPPEN BEFORE C14 Install and now it’s happening to BOTH my C13 and C14.
Hi @theRoyal1 ,
Which of the C14 demos did you load up and try to play (IIRC, there are several)?
Thanks!
there is an update available now, give it a try, I haven’t had chance to test it on many projects yet myself so the jury is still out for me. The current project Im working on seems to perform better though, Ill try it on a few other projects later and see how it goes
1 Like
Not a Demo track, Demo version of Cubase 14.0.10
I’m done paying. Until updates work solid enough to use I will be trying Demo versions… if it expires then I’ll wait till the next version.
I need solid more than I need new color gradients… 
1 Like
Thanks for clarifying, @theRoyal1 .
It just occurred to me that a good use of the Demo tracks might be to see if the computer can handle a “typical” project, if that’s indeed what they are.
I might go do that, though I’ve already purchased/committed to C14 Pro (no prob handling a fairly lightweight project).
ADDENDUM: I just played C14 Pro Demo Project Mendel Bij, about 1 GB on a very old ADK music computer (c. 2014), and the ASO Guard max was quite low about 7-10%, and the others were hovering around zero.
But I realized it was apparently mixed with only Cubase plugins, and probably mixed with a goal of being as easy on the computer as possible, so it might not be a good test to predict how C14 Pro would work on “real life” projects.
Still, I was pleased that this old rig didn’t melt down when it played it!
1 Like
So I see I’m not the only one who is disappointed by C14 pro. Even the first maintenance update last week ain’t stable. Glitching and dropouts randomly.
Thought I made a great track last Friday but then it started: hell on my ears. I thought it was Pigments (3 tracks with chords) was too much for it but even the Diva made me seriously disappointed. Today I was not able to make time to search on cause I was still grumpy…
My (new) system is on a desktop: i9 14th gen (14900F) , 64GB DDR5, 6TB M2 and GT730 VGA… Coust me a lot (and so did C14 and the vst’s) so I hope Cubase will come with an update that makes the troubles disappear… I think they’re must.
2 Likes
The amount of issues I had with 13 was already painful, now with 14 it’s just unusable, I literally can’t use it anymore. I’m a hobbyist, and I swear when you spend a hour in front of a friend who comes to record for fun, trying to fix it, is really annoying. You can’t trust your tools, how is that possible, why did they roll out 14 when it’s definitely not ready
Edit: I’m not going to put this on steinberg, I realized every software company out there have the same issues, it seems like nobody can maintain their softwares anymore, but they all still require you to pay to beta test their broken stuff. Nobody can code a driver anymore, please just hire veterans at this point, and pay them well
1 Like
I agree, its just not acceptable, why should we pay to be beta testers ?!
Things do seem to have improved with the latest patch (for me anyway)
Nut I still get spikes when mastering with Izotope (no noticeable audio dropouts though)
I havent had chance to load up some different projects that I originally had major issues with, but to be honest I basically had to freeze all the VSTs anyway just to be able to work on the track. A new track Ive been working on with 10 vst tracks seemed to be OK, but that could just be down to the VST’s I used
The same
For me it was the energy settings in Windows that was causing the constant stuttering and drop outs. I had previously changed it to High Performance and switching it back to Balanced solved the problem for me. Also make sure to diable energy saving and sleep mode.
One would think High performance mode would be better but apparently not.
1 Like
There has been a noticeable improvement since the patch update but I still find myself having to freeze way more tracks than I used to in cubase 13. In my opinion, 13 was better than 14, thats my experience
I need to have high performance mode enabled. That way I normally don’t run into problems. But it’s not ideal when being on the go because I need to have my big old charger plugged in to do that.
In regards to Microsoft Windows, Steinberg needs to start getting users to create trace files with the debugging / analysis tools provided by Microsoft such as the Windows Assessment and Deployment Kit (ADK) and Windows Performance Analyzer (WPA) etc. and troubleshoot peoples system issues. The high amount of DAW performance issues that people experience on various hardware configurations is pretty ridiculous. We need some real trouble shooting and real solutions.
2 Likes
I’ve run Cubase for many years on a high spec PC running Win 10. I had no issues with Pro 13. The first time I ran Pro 14 everything went right.
I later reopened Pro 14 and a project I was working on and immediately experienced horrendous dropouts coming in a cyclic pattern. I shut it down and opened Pro 13 and opened same project and again dropouts.
I then opened a older project in Pro 13 and there also were drop outs.
I rebooted and opened Pro 13 on both projects and they ran without dropouts.
I closed Pro 13 and opened Pro 14 to the project previously dropping out and it ran as expected for about an hour. I left for some other tasks while leaving the project up and running. When I came back to the project there were now dropouts.
I rebooted and opened Pro 14 and the same project and there were no dropouts.
I closed Pro 14 and opened Pro 13 and there were dropouts.
I rebooted and opened Pro 13 and opened the project I’d started in Pro 14 and no dropouts. I repeatedly closed and opened Pro 13 and various projects including the one initiated in Pro 14 and no dropouts.
In painful conclusion Pro 14 sets of some process when opened in Windows 10 that destabilizes the interaction between the program and the audio drivers. And it is totally useless to me.
For the curious I also use multiple DAWs including the sometimes known as sensitive and flakey Pro Tools Ultimate 2024.12. They all run rock solid with high plugin counts on both my RME USB MADI and UAD Apollo drivers.
2 Likes
In my experience. Since Cubase v7, I have built 4 new computers (Intel / Windows) and Cubase has NEVER been exceptionally stable on any of my computers and I have also witnessed instability on some of my others friends (Intel / Windows) computers aswell.
I’m not a noob with computers either, I have a lot of experience and I take tremendous care to do everything correctly and if I experience DAW instability than I will have a look into some DAW specific Microsoft Windows optimization guides (typically guides written and published by the DAW developers themselves) and nothing ever seems to work.
Previously I had a Presonus audio interface that worked completely fine, but one time after a fresh reformat / reinstallation of Windows it randomly made that Presonus audio interface start to crackle and pop from then onwards and I couldn’t find a solution. As a result, I ended up purchasing a RME UCX audio interface due to driver support / stability reputation and I have never had any crackling / popping audio issues ever since, however the Cubase instability issues always remain.
Just recently, I have discovered that the Kilohearts Snap Heap VST plugin is now causing my Cubase v13 audio to drop out. The issues with Cubase just never end !
From what I have tested, FL Studio and Ableton Live do seem to be more stable than Cubase on my computers.