Cubase 10, Windows 10 and multi-core (14+ cores)

thanks for this. It’s the first real TR /Cubase 10 test I’ve seen from a user so it’s great to get some real world feedback on these CPU’s.

Keep us posted on your results.


I just bought a new system with a AMD Classico Ryzen 1920X [12x 3,50GHz] processor and Windows 10.
Can I fully take advantage of the 12 cores, or are there limitations?
Is there something in that context which I have to take care about when installing Cubase on windows 1o?

Pops and cracklings lots of real time peaks after loaded 6 synth!
I7 7820x 16gb ddr4.
Turned off C-State and Speedstep. Same result.
Cubase 8.5 run soooooo smooth.
But this version is horrible.
Not working for me so far.

Quick update – I already mentioned in this thread that my 10-core Xeon has seen an improvement with Cubase 10, but I just built a relatively affordable 8-core 9900K workstation and it works even better. To my surprise, when tested with RME USB (especially at lowest latency), it was noticeably more powerful than the older 10-core Xeon – more than I expected – and completely glitch-free with Cubase 10. Was able to push the system further and harder than any prior DAW, and it has been amazingly stable and responsive under high load. Cross fingers it stays that way! Time will tell as I get into huge projects on this system, but I’m highly optimistic and I think Cubase + 9900K may be a match made in DAW heaven. Have not tested C9.5 for comparison, but this combo seems to be – so far! – the most powerful, responsive, and stable system I have ever used for music/sound. Also huge improvements in Studio One and Reaper. Haven’t tested Pro Tools and Nuendo yet.

I think I can finally weigh in to an extent. I ended up getting the big daddy - i9-9980xe, with 16 gb ram. I’m running intensive additive synthesis so it uses a fair bit of CPU in my projects plus a fair number of VSTs. My current first test project since I set up this system is underway. I’m running right now at Cubase consuming around 40% of my CPU in Task Manager. Zero dropouts or abnormal behavior. So far this is the smoothest DAW I’ve had and I’ve been recording since the 90s. Maybe that’s because I have a monster CPU now. LOL.

I have multithreading disabled so I am essentially running an 18 core system.

I’ll update if my projects get sufficiently more complex to tax my system further or I run into any abnormal behavior.

Very interested in the i9-9980xe results!
Which CPU cooler are you using and how hot does that chip get under an intensive session?

I think you mean hyperthreading, right? I’m jealous of your setup!

I have a similar setup… it’s just a little older but with a little bit more RAM. Since you have HyperThreading disabled and a similar setup, I have a question.

When I had HyperThreading disabled, I had an unexpected side effect… the current project had no audio anymore. There is nothing reaching the Standard-Out. New projects worked as expected but the old ones don’t. As soon as HT was enabled again everything worked as expected. This audio issue is on my system reproducible and is only related to HT.

Did you (or somebody else) encounter a similar behavior when HT get’s deactivated?

As soon as I am done with this project I will also deactivate HT since the Cubase performance boost is just unbelievable!

I hope that Steinberg keeps working on the workload topic. I like working with this DAW, but the fact that Cubase 10.0.10 introduced a fix so that only 28 real time threads (14 cores) get used, is hopefully just a workaround. The ASIO-Guard is in my opinion as well a workaround related to hardware. The above mentioned performance-boost could be related to the workload preparation that is not ideal. My above mentioned Cubase 10.0.15 behavior points out that low-level workload information get stored in the project and in summary I have the impression that the Cubase workload management suffers from a legacy software architecture.

Regarding this topic I am currently not happy with Cubase, because my hardware is not fully supported,… but the good news is… there is room for improvement!

Yeah hyperthreading is what I meant. As to the other questions, I’m using a Noctua NH-C14S air cooler which fits my 4 unit rack case. It’s idling around 52°C package temp with so far up to ~50-60% CPU use and zero noticeable fan noise while the lid is on. If I take the lid off the temp drops to the high 40s. All of these are comfortable temperatures for me.

At least from my use there’s no reason to get a water cooler. Especially in a studio where you need silence this works just fine.

Regarding hyperthreading disabled - I have observed no abnormal behavior with hyperthreading disabled. I would want hyperthreading disabled regardless as some of my synths use a very large amount of CPU in a single thread and I need each thread as strong as possible.

On topic for the thread I will continue to stress my projects a bit more but I don’t think I will use much more CPU overall in any practical sense. I’d have to create a torture test project to go much higher and I don’t see the point. From what I can tell everything is working fine.

This is definitely from my experience a very good CPU for audio and it’s taken any stress of running out of CPU away from my mind. Most people will never need this much CPU ever for any reason. I will update if I run into any trouble.

fwiw, I have the 7900x running all 10 cores at 4.3 ghz, and I have noticed that hyperthreading is actually pretty effective in Cubase 10. I tried disabling it, and it appears to drastically increase CPU load and “average load” in the ASIO monitor. With hyperthreading on, the cpu load is lower and it seems to have a lot more headroom, and is utilizing the threads in such a way that it’s acting sort of like 20 cores.

I keep hyperthreading on because it actually seems to benefit cubase 10 in my experience. Granted, these are just test sessions and I haven’t tried a massive project yet. The results of that have yet to be seen.

This is strange… that is the exact opposite experience of mine. I try to find a pattern but the only difference I see so far is that you have less than 14 cores… but does that really matter that much?

I hope you can test it on a normal project and that you post your experience.

Hyperthreading should be On.
If that somehow decreases performance, then something somewhere is wrong.
From my own tests and from what I can read on some of the more well known DAW computer manufacturers. A gain in performance around 40% up to 70% is not uncommon.
I would be looking at bios updates, drivers or even a fresh OS install if I had worse performance with Hyperthreading ON.

Hyperthreading should be On.
If that somehow decreases performance, then something somewhere is wrong.

Unfortunately, it’s not so simple. It depends on what you understand for “better performance”. If you disable Hyperthreading you give more time to the different cores to synchronize their threads, so it’s very likely that you get better ASIO performance (less clicks) at very low latencies, especially when playing VST instruments. However, if you’re at the mixing stage and higher latencies aren’t a problem, then yes, Hyperthreading can give you a boost in performance, usually no more than 20% in my experience.

Yes if you want to run at extremely low latency, HT off might get you room for a few more vst instruments.
But then I would suggest a low latency audio card like a RME would make a bigger impact.

So is it safe to go with a 9980XE now? @mikejm’s experience seems positive, but hyper threading is disabled. Is that still necessary for C10 to work properly? I’m planning a new PC build for my main midi composing workstation and would like to go with the 9980XE but want to make sure that Cubase will take full advantage of the new hardware.

No… Cubase does (currently) not take full advantage of the hardware. Not if you have more that 14 cores. Never the less this CPU has so much power, so that your bottleneck(s) will be else where. I have a better Cubase performance once HyperThreading is disabled, but it’s more than sufficient if HT is enabled. Working with that power is very nice.

But if you build a new PC and you only care about Cubase, then 14 cores is the limit. If possible choose a CPU that has a high frequency (and choose a silent water cooling.) In the german forum somebody has posted his hardware That could be interesting for you, since the onboard Graphic-Chip is sufficient enough. If money is an issue, then his setup seems to be an excellent choice.

Thanks for the info! Is Cubase unstable with your CPU with hyper threading enabled? Or is it stable but just doesn’t take advantage of all of the cores? If Cubase is stable then another option for me would be to use VE Pro to host sample libraries outside of Cubase.

No no… that has nothing to do with stability at all. Cubase 10.0.15 can only use 14 cores due to a change of the Windows 10 Multimedia Class Scheduler Service (MMCSS). Cubase 10.0.15 runs super fast and stable on my system!

In a project that has around 70 tracks my realtime load is lower than 5% with an average load of 50%. Occasionally I might have a realtime CPU peak. Once I turn HyperThreading off the average load drops to 25%… but honestly I can not explain why.

With the new processor the performance will be even better, since the new Intel Core i9 XE has a higher base frequency… but the Intel Core i9 XE processor is way too expensive.

Ok, good to know that C10 is fast and stable on your system. In the 70 track project that you mentioned, are those instrument tracks with VI’s/samples loaded? Or audio with plugins etc?

I agree that the i9 XE is expensive, but the rest of the build is going to cost a lot so it’ll be worth the premium for the 9980XE for me.


this is information is only correct up to Cubase 9.5.
This very thread was started to collect impressions on how Cubase 10 works on machines with 14+ cores, as it no longer addresses resources like 9.5 and earlier did.

The article dealing with the MMCSS issue has been also updated with the sentence quoted below: