I havent changed any settings in my PC i havent added anything to the project and it has had zero problems untill now. I opened up my project tonight and it was instantly in the red “processing overload” ive been working this same project for weeks without any issue it literally just started happening.
Ive maxed out the buffer size to 1024 no change. Ive even removed several channels of instruments attempting to eliminate a possible CPU hungry VST even though ive had this full project running flawlessly before tonight. Im literally down to a couple of channels of drums and bass and a couple of guitars and still it spikes in the red.
The only thing that has changed is my new Apollo twin interface but that has been working great for a few days since ive had it without any issue.
Ive activated and deactivated Steinberg power scheme with no change on either setting. I feel like its right on the verge of a crash.
This has me baffled.
It doesn’t look to be a Cubase problem from what I can see. It looks as though you’ve got background processes running that have delayed procedure eating up valuable time.
My first suggestion would be to reboot and see if the problem persists. Secondarily, you could try disabling the internet during your session and see if that helps.
Every time.
I had this problem a couple of weeks ago, it happened with Cubase 13, and with the issues with C13, I closed it and opened Cubase 12 and thought to just carry on working, but it had the same problem - massive spikes such that the project wouldn’t even play and the audio meters going haywire. So I tried Cubase 11, same thing. A reboot set things back to normal. Still have no idea what caused it.
(Windows 10, i9 12900, AMD 6700XT, RME AIO PCIe card, 64gigs RAM, 512 buffer.)
I have just started having the exact same problem, and it is doing my head in. A song that was previously fine is now maxing out on audio performance and is effectively unplayable. I have switched off all startup apps, freed up 150Gb of hard disc space and moved everything on my remote disc to a brand new SSD. Still not working. Disabling all VSTs on startup seems to help, could it perhaps be a vst issue?
Hi Bill, Yeah, I,ve been climbing the walls with the same thing. Audio dropouts and the audio meter consatntly pegging. It’s rediculous. I think Googly-Smythe tried ty help me a while ago with this as well. I’ve been on the phone with Steinberg support and one of the Tech’s Tim, was able to find a couple things to adjust under the “Studio set up” tab. This, I think, at least got rid of the annoying white pop up box, Audio dropout detected… Did not get rid of the drop outs or spikes, but I gave Support the logs they needed to look over what was happening on my system when it does drop out. This was a better part of 2 weeks ago and i’m still waiting to hear if they found anything helpful in the logs. I also showed them the “LatencyMon” Reports on what may be causing the whole problem, but they haven got back to me yet. If they get my situation cleared up i’ll certainly share their results. For me,… I can’t record anyone or have anyone at the studio until I get this cleared up. It’s embarrasing to have these issues live while in session.
Chuck, ( PC, Win 10 Pro, 11th Gen Intel Core i-7, 11700K, 64 bit. 128 G.ram)
Hello jinkyea,
The 11700 is pretty straightforward it should work smoothly.
I can check your LatencyMon report.
Was the system running good before?
Have you tweeked some settings in the bios?
C1 state , speed stepping etc…
Are the drives sata or nvme?
The drivers cause lantency. For example when using only Nvme ssd’s, In device manager disable the sata controllers. Most of the times the motherboards have at least 2 different sata controllers.
Disable the ones that are not used.
Chuck, I finally got to the bottom of this for my system (PC, win 10, Intel core i9). I am running a laptop, and it appears that the system had “decided” the power supply was dodgy. It was working fine (I know this because the battery doesn’t work) but I suspect the system decided in its infinite wisdom to throttle the CPU to conserve power. Long story short, I changed over the incoming power cable and adapter and bingo, most things are working fine. I now have a secondary problem in that about 50 Native Instruments VST’s are blacklisted, and I suspect that has happened as a result of my mucking about trying to sort the original problem. But, audio glitching is gone! I wish you luck with your issue – hope you get a speedy recovery.
Wow, That’s good news. Dig it! Yeah, I have the Izotope music production suite and there’s always something that hijacks my time if i want to sit with a complete set of working plugs and instruments.The aquisition of Izotope by Native wasnt a smooth ride for me either with the passwords (because i had NI plugs from yearsd ago under a different account). So good luck with resetting all those. I will say that the Izotope IT/ support staff are top notch, so maybe throw the issue at them and see if they can quickly fix it up for you. For me,…well,…I’m still getting more and more info to Steinberg/ Yamaha support so they can determine,(Hopefully soon) what my uissue is. Don’t have Cube 13 pro on a laptop, just a desktop. It’s a bicth. I can’t have clients in until this is rectified. Having to use Cakewalk of all things to keep moving.
Hey, Hello OLIZ,…so sorry to get back w you so late. Thank you. I just tried disableing the extra 2tb hard drive in the computer. This desktop has a 2 tb SSD nvme plus the extra disk for storage. I have tweaked some items i felt comfortable tweaking,…i upgraded ther ram to 120, i did replace my usb C cables. I had 2 plugged together to make the distance, but seen this was a no no,…so i got a premium single length cord to go between the desktop and the interface. It does have it’s own dedicated port on the computer.I do have the latest drivers for everything, tried all the buffer levels from 64 to 1024, same outcome. “Disable usb selective suspend”,…did that,. set the processor scheduling to background services, I did not disable any start up apps,…I don’t know enough of what’s needed for start up to jump in that side of the pool.I disabled the system sounds when i ngot the computer, so did that,…I have it on "custom Power Plan. I think thats all the tweaks i was able to do,…up to and including disabling the internal hard disk drive. Yup still dropping out. So, I have cubase 12 pro also and it didnt drop out until i got 13 pro??? so i went back to 12 and tried to record with that now, and of course, that drops out too. I gave the Steinberg/Yamaha support staff multiple sets of test projects with, and without the internet, 3rd party plugs, safe mode on and off, new fresh file locations, and the data logs plus the latency mon results from everything. Still waiting for Steinberg to get back to me. I’m dead in the water basicly,…since the beginning of this year. Im kinda fit to be tied. paid full price for 12 pro and the upgrade charge to 13,…can’t use either. but anyway, Hey, thank you kindly for taking your time to help. I sincerely do appreciate it.
Hey Bill, did you manage to get your plug in instruments reloaded? in the cubase 13 manual, it shows how to reactivate them from the block list. Page 869. Unless of course they were 32 bit, then you might be still having an issue, beacause theyre not supported anymore. I Hope you made out well.
That’s not good news. It’s rediculous that loads of people that had this issue have it cleared up now,…but trying their fixes doesnt seem to work for the remaining lot. I’d really like to know how many folks out there are having this drop out issue? Can’t be just a handfull.
Just saw the messages.
Just for a quick refresh… Win 10 , 11700k , 128GB of memory.
What audio interface you’re using?
How long it has been since you’ve installed Windows?
Yes If you can send the LatencyMon report might help.
the model of the motherboard and gpu.
For a quick test, just run the memory on 2 slots. (not 4 ) Remove the extra memory .
