Every month I take time away from Nuendo and try to work in Cubase 10.5. There are so many great features, and I especially like that the clip of any audio or midi I am currently editing gets highlighted in black, instead of circled in gold or red like in Nuendo, which I cannot see (being partially colorblind)
Anyway, my latest foray yesterday resulted in the same bugs that I have found from the first release of 10.5, in my opinion the most buggy version of any Steinberg software ever. I worked on my arrangement for many hours without any issues, but all of a sudden the CPU spiked so high that the song wouldn’t play, it kept stopping. I started turning off VSTi’s, plugins, etc. Nothing helped. I disabled instruments, muted folders, etc. Nope, CPU still spiking to the edge. I even turned the latency for my Scarlett Interface up to 2048. Nope. I closed Cubase and opened the exact same song in Nuendo 10.2.20. With the latency set to 256, the song played fine. CPU was down where I expected it, around 40%.
And so ended my yet again monthly visit to Cubase 10.5. Oh yeah, the song played fine in Cubase 10.0. Of course, that’s the last Cubase version that was reliable and stable for me. I’ve said it before and I will repeat myself ad infinitum - something is inherently wrong with Cubase 10.5 and it never gets really fixed with the updates, just smoothed over for a bit like a bandage on a broken arm. The arm is still broken, just like this version.