Thanks!
…and I would like to say that I never had any issues with Cubase beyond the usual Windows optimizing aspects that is as needed with process intensive software like NLE video editing, complex photo and graphics programs and 3D animation and CAD programs. As the power of PC’s have increased there’s more headroom available to minimize these things, but they can still exist.
Things like anti virus programs, etc have and probably will always be an issue. Most of all using an OS like Windows will also probably always create a imperfect platform. It’s the price to pay for using an OS that is not application and hardware specific, but able to run many types of programs and hardware… To have program specific systems and applications would be costing us 1000’s of $$$.
ElRey / Mystic and and Tote as well are the worse culprits , but you are on a different processor , the only way a test can work is like for like
Ive also noticed if i click any where outside the Cubase window frame ie go to the desktop Cubase quits without notice , i found this by mistake of wanting to turn off phantom power from a live recording on the RME , lost the recording
if you’re using a modern Intel CPU(12xxxx/13xxxx) then windows 11 is the way to go as it has the correct core threading needed for the P and E core allocation in programs. This is something Cubase 13 has adressed under the hood apparently, so if you’re on Cubase 13 and a new Intel then Windows 11 will give you optimal performance .
Step-by-step instructions are there for you. But because you mentioned this issue, it makes me think that this should be a feature request for Steinberg to add the number of CPU cores to use in the preferences, similar to how Native Instruments’ Battery 4 or other similar programs can be configured in their preferences.
Thanks I tried this, but didn’t know what HEX number to use to exclude only CPU 0. But I found this page to calculate the HEX value needed. Now it works. I paste below, perhaps it will help somebody.
Correction. It works with Cubase 12. But somehow I am unable to do it with Cubase 13. I used exact the same command line for C13 shortcut and Cubase 13 still opens with all CPUs active. In not sure why.
What’s more interesting - even when I disable manually in Task Manager CPU 0 for Cubase 13 process - after a while system activates it again by itself.
This speaks to my overarching point here at the beginning of this thread: how is it acceptable that end users are having to worry about things like hex codes? This should not be our problem.
The DAW makers need to take on a higher level of responsibility and solve these problems, even if that means pulling in the likes of NVIDIA or Microsoft or whatever RAID controller manufacturer or whoever is writing software that unjustly interferes with Cubase’s right to sufficient processor time. It should go with the territory.
