No i did not yet. Thanks for the tip, Twan!
Sorry if I missed this, but are you running the studio drivers for your RTX 5070? Or are you running the normal drivers?
Hi uarte, im running the studio drivers. Is that wrong?
No, thatâs good!
1 Like
Exactly.
Iâm just trying to run through the list of obvious things, and reminding you to make sure to run the studio drivers is one of many.
Looks like youâve done a lot of the right things. This one looks a little tricky.
HOWEVERâŚ
This is where Iâd try to focus. If LatencyMon is throwing any warnings, thatâs a problem I suggest you solve. Usually there is a culprit, and in my experience itâs often some misbehaving driver. And it can be tricky to definitely determine. HOWEVER, the fact that itâs NOT doing it during testing of other DAWs but it is ONLY doing it while running Cubase is where I suggest you focus some more effort on solving this mystery.
I would look very carefully at what is different between when you run another DAW vs. when you run Cubase⌠For example, what devices are you using? What plugins are you using? Are you doing anything with the network or graphics card that is different? And so forth⌠it can take a while to dig in and compare the nuances.
In other words, I think there is likely SOMETHING that is being triggered that is different in your sessions in different DAWs. It could be a driver, multiple drivers, network, devices, controllers, extra apps that launch for whatever reason, plugins, etcâŚ
So to help diagnose, I suggest creating the MOST SIMPLE IDENTICAL possible test sessions in each DAW and compare the results⌠and watch LatencyMon carefully for every step of the way. Use the scientific method to help you⌠one tiny step at a time, document every little step, one track/plugin at a time, make sure you are using the exact same devices, drivers, etc., make sure you can replicate it, and try to create iterations of increasingly complex (yet still identical) projects in each DAW until you experience the unwanted behavior.
If you do that, you will at least collect more clues, and possibly find the culprit. My guess is some device, driver, plugin (VST2, VST3, ARA), or external app is being used differently.
The reason I suggest this route of examination, is that I have used many DAWs for many years on the same machine (although nowadays Iâm highly focused on Nuendo), and it is somewhat rare that Cubase/Nuendo will behave the way you describe while other DAWs on the same machine (using the same drivers and the same plugins!) will perform notably differently with regards to LatencyMon, not accounting for their typical engine differences (i.e. within an expected normalized statistical performance curve).
SIDE NOTE: Some DAW graphics engines and plugins do behave differently in terms of how (and how much) they use the graphics driver, hence why I mentioned you should be using the studio driver, etc⌠Graphics drivers are notorious culprits of DPC latency problems with DAWs BTW. I actually switched all my machines over to AMD graphics cards since I found them to be more stable for DAW work, but if you use nVidia, you really need to use the studio driver, not the regular driver, for example. So itâs good you do. Also, you have a more recent gen graphics card, so itâs possible even the studio driver wonât prevent some DPC latency issues to creep in. One additional possible test later on, if all else fails, is to test out your machine with a different graphics card. I use older gen AMD Radeon Pro graphics cards in my DAWs on purpose, as they have been totally rock stable for DAW work with drivers that focus on stability instead of performance, for years and years. YMMV, but I did have many more issues with nVidia, especially when I chased âperformanceâ with the âlatestâ gen. That may or may not be an issue here for you, but something to consider at some point if you canât find another culprit.
Anyway, the primary tests I suggest you explore stem from the fact that you say that LatencyMon is throwing up errors ONLY during Cubase. To me, that is a big clue that something in your other testing is probably not consistent. Find the differential between your DAW sessions in different DAWs, and youâll probably find the problem.
Best of luck!
3 Likes
Thank you very much for that detailed advice uarte. I will hit back here when i have some news. may it could help other people too. I will take your advice and do that testing.
Cheers
1 Like
Hello,
The new Nvidia RTX 5000 series might be causing the spikes.
Iâve been having similar issues since I upgraded from a rtx 4070 super to rtx 5070Ti.
I have a AMD 9900x chip everything was running flawlessly and smooth until I swapped graphics card.
The problems Iâm getting is not specific to one software, it can also occur just by being on desktop mode scrolling webpages. Most of the time in windows anything related to media like audio, images or.video. I can get random lag or sudden micro studder that last a second or two.
Also sometimes by opening an application the mouse would freeze for a second giving the time for the app to open. Its very annoying!
What Iâve read is something related to the slot of new pcie 5 and the new rtx series and its drivers.
Anyhow will see how things will go with the next drivers.
I tried the april 16th drivers on the Nvidia site and the april 30th drivers still having the same issues.
Releasing driver updates in such short period to me would translate to:
They worked on several fixes but yet left some behind unfixed. Thats my impression. :))
Thats a very good input here OLIZ. After all i have done, tested and tried i think it is well possible that its a GPU issue. I hope some future driver update can fix it. Bu for now i guess i will switch to Studio one. I just wasted too much time already on Cubase. It is very dissaponiting for a 20 years Cubase user to see that its the only DAW having that problem. The others were able to fix this.
Thank you
1 Like
that âcanâ help
Itâs entirely possible that Cubase is to blame, but based on the info youâve provided in the thread, Iâm not sure you definitively proved that Cubase is the culprit yet. Moreover, the implication that the other DAWs were able to âfixâ this implies they actually did something to âfixâ something, when it could have nothing to do with any of the DAWs in the first place, but rather an errant driver, device, plugin, etc., as I mentioned previously.
And respectfully, letâs not get ahead of ourselves and give credit (or criticism) to developers for âfixingâ or âbreakingâ things when it could be a combination of complex factors or more likely the culprit of a lone driver that is misbehaving in certain specific circumstances. You do have a tricky case here, I agree, but you already saw my recommendation of how to proceed with your investigation. And sure, I understand if you want to give up and move on. I might have done the same thing. But please donât go assuming one DAW âfixedâ something or âbrokeâ something, without empirically knowing what they actually fixed or broke. Science and facts first, is my motto! 
Again, itâs entirely possible that Cubase is to blame in your case, of course, and do what you want re: using another DAW of course. (I used many DAWs for many years and was very happy switching around.) But for people who find this thread, itâs important to point out the many other possibilities.
Cheers and best of luck no matter what you decide to do!
3 Likes
Hi Uarte,
i agree to some point. Its a bit difficult to blame something when its not even clear what the root of the problem is. Yes, i dont know it, but i just see the facts so far. S1 and Ableton work, Cubase doesnt. And the crazy thing is, its even with a Steinberg interface.
Sadly (or not), our time here on earth is limited, so its the most valuable asset we have. Im not willling to endlessly testing on without any security that i reach the goal.
I like Cubase and i know it in and out, but in my case it doesnt serve me anymore at this point. I was reading around more and some people report, that there are problems with Nvidia cards and Cubase. Maybe if i read on enough, i will find people reporting problems with Ableton and AMD cards. I dont know. It is how it is. I want to make music and not digging in BIOS, Windows or any settings somewhere. S1 is not Cubase, but it is the closest i guess. And it works properly. Thats what i need now.
Thanks to anybody helping. If i find the solution, i will keep you all updated here and maybe it will help somebody else.