Has anyone tried asio4all? I will try tonight
I have not had a chance to try Asio4all as i was trying to fix a problem with Automap not working with Cubase * (which i have now resolved).
Reading through posts on here many people are suggesting that the problem with these spikes is down to Nvidia GFX. Even if this is true (I have MSI Nvidia GTX670) this is not the fault of Nvidia, its Steinberg. All other versions of Cubase have run without fault with the same GFX card, infact I have been exceptionally happy with performance given I am 90% VST with a couple of vocal tracks. I have never been in a position to have to freeze tracks, although I have done this out of interest and seen a massive immediate drop in the performance meter.
So if this is truly an Nvidia/C8 issue do Steinberg think it reasonable that people forking out good money for upgrades which are supposed to be improvements and not render your system useless to have to fork out for a new GFX card at each upgrade?
I realise that the majority do not have these issue nor an Nvidia card but that is of no consequence as next update it could be that they screw up the system working with another GFX card.
Imagine us guys (and girls) with this issue biting the bullet and forking out for a new GFX card and the next upgrade they does not work with this?
If this issue is down to GFX cards and I have read in the past other problems with particular GFX cards then its about time that Steinberg recommended a handful of cards that do work without issue. There are some people who like to play the odd game to relieve the stress of using Cubase (certainly this current C* release) and therefore choose a high end GFX card to run the high end games. Other are happy with a mid range card and other will no doubt be happy with the cheapest card possible that will run Cubase ok.
Rant over, I am going to log this as an issue as we do not seem to be getting any further forward. If I am expected to re-install 7.5 to fix the issue I then expect a refund for my C8 upgrade or a credit to the value for the next release.
I think this perfectly reasonable.
By the way mine happens every single time I change a patch on a non Steinberg plugin. Also with next to nothing running the VST performance meters are bobbing about mid way when i never usually see them move beyond 25% even with a heavy VST presence.
I am experiencing the same issue (W7 64) on two different computers (one with NVIDIA Quadro 4000 and Phenom II and another with NVIDIA Quadro K5000 and i7 4690). I saw it during the last year with cubase 5.5 and now with cubase 8). Always the same: Spikes/freezes type of issues in no matter what type of projects.
Interestingly: If I revert to NVIDIA Quadro Driver 312.69 WHQL or earlier the issues dissapear immediately (even without rebooting). Installing a later driver brings the issue back for me.
As far as I know Cubase is using OpenGL drawcalls (i think for the GUI and the video renderer that seems to be running even if no video content is used). I remeber reading a release note or something like that that NVIDIA changed something with OpenGL commands or command handling somewhere around the driver revisions 3xx or so. I also saw graphic driver related entries in the system event log on the older machine that correlated to the spike issues in my DAW. Not on my new one though that I am currently using - but nevertheless the symptoms look exactly the same.
Maybe someone can solve it the same way - though it’s kind of annoying to have to stick to outdated drivers…
I think the issue with me is solved
BON-5544 PERFORMANCE: Fixed an issue with ASIO peaks when using audio drivers from RME
560ti, 347.52 same problem.
I’m running Cubase Pro 8 with SPL Crimson, and had that very same issue, but then I tryed A LOT, and last I tryed to remove the ASIO Guard, and everything just ran from there!
Give it a go in Device Setup, hope it worx for ya…
Cheers from Copenhagen
The core parking fix helped me a lot with the CPU spikes.
Hmm this is a suggestion I have not come across before. I will try this when I get home. Have any of us Cubase guys tried this with success?
I kissed the ground in gratitude when I found this thread. Thank you Laurie for your great diagnostic work and writing it all up in this forum. It saved me days, maybe even weeks of work.
I work on a Lenovo 520, which has two built-in display cards, an Intel HD 3000 and a Nvidia Quadro 1000M. I was playing video games during an interim, and updated the driver of the Quadro so I could play on the second monitor. That proved to be fatal when I returned to Cubase. Fortunately, all I had to do was roll back the driver for that video card, and everything worked again. But I shudder to think of the time I would have lost and the software mayhem which would have rolled through my system had I not found this thread.
I had the same problem as all the other describe. My System is equipped with a K2000 Quadro and a Samsung 1TB SSD. I try all the things from this post also a new driver for the Quadro card but there is not such an old driver available because the card is brand new. Nothing helps, still processor peaks to 100% for 2 to 10 seconds. The last thing I try was to disable the sleep mode of the cores and it works perfectly for me . Since 3 days and a lot of playing no peaks anymore and I also notice that the whole system seems to be more stable. Hope it works also well for the other here in the forum.
PS sorry for my bad english !
The Peaks are back
So the processor sleep Option is not the solution
If you get spikes with just a few tracks playing it might be a bad driver - try running DPC checker: http://www.thesycon.de/deu/latency_check.shtml while Cubase is spiking. If DPC checker is complaining (by displaying red bars) try to find the culprit with http://www.resplendence.com/latencymon (also while running cubase).
Edit: FWIW. Cubase 8 runs fine - much better than c6.5/7.5 ever did. And I’m really impressed by how cubase scales with multiple cores.
I see most in this thread are pc based machines. I’ve been on a macbookpro for quite a while and had ALL the same issues I’ve read in this tread and others regarding the spikes. Cubase was unusable to me almost the entire month of January and into Feb. I was getting ready to (gulp) switch to Logic after fifteen years on Cubase it was so bad.
The reason I bring this up is because I finally updated my OS to Yosemite although Steinberg warned against it at the time. to be honest, it couldn’t have gotten worse. I also had cpu system freezing spikes with just a few vsts loaded on a new and empty project. Yosemite cleared up almost everything! I’ve been 80% happy with my setup. I still have more stuttering than the past but “render in place” saves me hours and HOURS of rendering large pop and orchestral projects that I was “hanging on” to the idea of making version 8 work. It’s been working for the past three months consistently.
I bring this up because my 2012 Mac has a NVIDIA GeForce GT 650M stock in it and it was the OS that changed everything on my end. I know several guys have had supposed NVIDIA issues.
Not sure how this may help a non mac user but it’s info to throw into the discussion.
CCF, thanks for this awesome post as I am having similar issues and have contacted NVIDIA. A very helpful support tech has passed this onto the team and they are looking into it.
The thing is - ProTools video performance is so much better now as far as I can tell, and also in Nuendo it looks smoother (I had had to disable AERO before to get playback without micro stuttering, but that resulted in tearing due to disabled v-sync) and better but Nuendo hangs every now and then.
Hoping for a fix soon!
I have exactly same problems on a new MacBookPro 2015 i7 quadcore and 16 gb of ram, it is unbelievable.
I spent more than 2500 € for a laptop and I cannot use it with Cubase.
Also, I have to say, Steinberg assistance is near to 0, you have to wait 2 months to have a reply by email, so I suppose I have to close my studio for 2 months waiting for a Steinberg reply?
I really think this will be the right time to switch to another software.
Anyway if someone can help will be appreciated.
first response from NVIDIA: try drivers 337.88
They work for me and give the same smooth and solid video performance I experienced in the newer releases, but without the CPU spiking as far as I can tell right now.
Hope they can fix it for future releases.
And hope this helps some of you.
Thanks a lot Laurie for sharing your Solution!
I had the same problems, massive CPU spikes freezing my system, recording was impossible.
Now I just uninstalled all NVidia drivers, so that windows 7 automatically runs it’s own certified drivers.
Problem solved and saved me a huge amount of time for testing other settings
I am in contact with nVidia (still) and now Dell, my supplier… it looks to be a CPU chipset issue.
Questions for you:
- do you have Intel chips?
- do you have any Intel startup processes or services DISABLED?
I feel like I have solved it at my end by re-enabling the intel services and processes on startup and will see if I can find the one that is causing or rather solving the issue when I have time soon.
It may be you might be LACKING an Intel bundle that does the GPU handling (as intel chips often have GPUs onboard).
As for the drivers: 337 worked for me but I prefer the performance of the latest drivers - therefore I’m still hunting this down.
Hope this helps so far… will let you know what I find.
I have same issues and have done everything including a full format and re-install but just same.
I took my nvidia GTX card out and replaced with on board graphics but just the same.
I am having to many problems with Steinberg that I am seriously thinking of moving to another Daw.
Trouble is I have invested a lot of time and money and don’t know if I can even resell Steinberg software?
I am in contact with all kinds of support teams and seem to have find a workaround fix for me at the moment - though I am still checking to see if it is a long term solution.
What I did:
- disabled processor C-States in my systems BIOS
- https://bitsum.com/parkcontrol/ downloaded this and set a power profile that does not park CPUs.
- disabled C1E states with “ThrottleStop”, though I assume this is done anyway by the BIOS setting.
If you guys have the chance to do this and feel confident, give it a try. This might be it . . . at least as a workaround until the devs find out what is sending the CPU to sleep every now and then…