Not at all! I use a Ryzen 7900x and not had any issues at all in terms of CPU spikes. There has been the odd update back in Cubase 10.5 when I had a Ryzen 2700x which spiked but I was really pushing that CPU. All good though with 13. No pops, not driver issues and no random red lights of doom whilst idle which I've had with other DAWs.
Lucky you :( @@thesampleist there are a few lengthy threads on Steinberg forums about that. It's unusable for me now. The same project runs miles better in Studio One, same tracks, same plugins, no issues. Apparently, it could be that Cubase still can't utilize Intel's cores properly. So it overloads Core 0 while not distributing the workload to the rest. A project with 15 tracks constantly goes up to 80% CPU load. Task Manager shows that CPU is barely doing anything, though. It was not a problem on C12.
Am I going to lose any of my music/audio files from my Cubase 11 Pro if I will upgrade to the Cubase 13 Pro…? (and I’m asking for an answer:- let’s pretend I’m just doing an upgrade to the 13 Pro- so what will happen with all my recorded music and all those tracks in the Projects l have under Cubase 11 Pro.?…)
They removed the undo redo functionality for 3rd party instrument plugins for some reason. Till Cubase 12 it would work perfectly on all parameters that can be automated.
Cubase ist very stable and you don't need a sandbox unless you are using buggy non-compliant VST3 freeware. I've only had two crashes in the last 8 or 10 years. and it was due to a third-party buggy plugin. Nuff said....
Any CPU spikes? I stopped using Cubase due to it.... It's ridiculous. And I have an new i9
Not at all! I use a Ryzen 7900x and not had any issues at all in terms of CPU spikes. There has been the odd update back in Cubase 10.5 when I had a Ryzen 2700x which spiked but I was really pushing that CPU. All good though with 13. No pops, not driver issues and no random red lights of doom whilst idle which I've had with other DAWs.
Lucky you :( @@thesampleist there are a few lengthy threads on Steinberg forums about that. It's unusable for me now. The same project runs miles better in Studio One, same tracks, same plugins, no issues. Apparently, it could be that Cubase still can't utilize Intel's cores properly. So it overloads Core 0 while not distributing the workload to the rest. A project with 15 tracks constantly goes up to 80% CPU load. Task Manager shows that CPU is barely doing anything, though. It was not a problem on C12.
i9 here too! with last updates zero cpu issues. very stable so far.
@@Byron101_ It's been an absolute stellar experience for me! It's not even crashed when shutting down either! :D
how do you edit your screen recording to do these zoom angles in the beginning in the video ?? plz
Am I going to lose any of my music/audio files from my Cubase 11 Pro if I will upgrade to the Cubase 13 Pro…? (and I’m asking for an answer:- let’s pretend I’m just doing an upgrade to the 13 Pro- so what will happen with all my recorded music and all those tracks in the Projects l have under Cubase 11 Pro.?…)
It will still work, just open the project like you normally do…It’ll automatically detect it.
They removed the undo redo functionality for 3rd party instrument plugins for some reason. Till Cubase 12 it would work perfectly on all parameters that can be automated.
Does Cubase sandbox plugs like say Bitwig?
No
Cubase ist very stable and you don't need a sandbox unless you are using buggy non-compliant VST3 freeware.
I've only had two crashes in the last 8 or 10 years. and it was due to a third-party buggy plugin.
Nuff said....