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

Fabio, does this mean that we can expect new improvements related to multi-core in the coming Cubase 10 updates?

Hi Jorge,

no, the fine tuning I was referring to is already in place, but we (at support) are waiting for a more detailed documentation on how to actually configure the switches correctly.
This does not exclude further improvements, that’s something that needs to be done constantly :slight_smile:


so I did some tests with my recent project (started in Cubase 9.5).
I could not observe any difference b/w C9.5 and C10 for this project, wrt dropouts/overload.
Overloads at same time in both versions (skips Audio and or automation in that case)

  • i7900x, 10 core HT, GTX970, Win10 1809, SSD, Cubase10, RME babyface, all latest drivers/versions
  • Project is loaded, will only run hassle free with AsioGuard High and 1024 samples buffer
  • will not work with AG low/mid
  • Several instances of Omnisphere2, Avenger, Geist, Effects on every track, some grouping, lots of sidechaining (to trackspacer, pro-c2)
  • Load meter is 100% for average, ~0% for realtime, disk spikes
  • Project plays (fine) without crackles (very few sometimes) in that state. If further things are added, it will show audio dropouts in both Cubase versions


How much is the cpu load with this project?

Cubase meter shows ~100% Average load continously, and 50-60 RT load when playing back
10 (20) Cores seem to be working b/w ~20-40% each in task manager

I made another weird observation: freezing one single track (Omnisphere 2.5) in this project does the opposite of easing the resources. The project becomes unplayable (only dropouts, i.e. will not even playback something, meters only flicker). Maybe any hints on this?

This could make sense only if you used a hard drive from the 90s :smiley:

I originally thought I was not experiencing any issues after upgrading to 10 Pro when I turned hyper-threading back on my 10core CPU, but something changed since then. I think a Windows 10 update may have broke something. If I do not disable hyper-threading, I get random pops and spikes. I don’t have time to fiddle around with it, so I just am leaving HT off for now.

Not used versions of Cubase 9-9.5. Tried to return to Cubase 10 Pro. I observe, like many here, the problem with random jumps of RealTime Peak, which after 40-50% of ASIO Average loads give clicks and spikes. The system is fully optimized, the latest drivers for all equipment are installed. The situation is slightly improved by disabling hyper-threading support in the BIOS. But does not solve the problem as a whole.
My system: Windows 10x64 Pro v1809, MB ASUS P8Z77-V, Intel Core i7 3770K 3.5Ghz, 16Gb RAM, ASUS Dual-GTX1060, Cubase Pro 10, RME Babyface, AKAI MPK261
I would not like to give similar examples, but I do not observe a similar problem in other DAWs. I also use the latest versions of Studio One 4, Reaper, Reason 10, Cakewalk BandLab. Therefore, I can say with confidence that the matter is in Cubase. In terms of performance and optimization, unfortunately at the moment it is inferior to them all. I look forward to future updates and solutions to these problems. Otherwise, figuratively speaking, why do you need a Ferrari, if it does not go! Good and good luck to the development team, I know that it is not easy for you now.

In my experience, getting real-time peaks is also related to having the GUIs of some effects open, in particular spectrum analyzers (Voxengo SPAN is specially prone to causing high real-time loads). This improves a lot if you disable hyper-threading, as it seems to give more time to the graphics environment.

disable record button on channel to remove realtime peaks. you ll see the difference

Yes, I knew that. Doing this effectively brings ASIO Guard into active mode, so it improves the performance as the system then plays at the additional latency dictated by ASIO Guard. Anyway, in my particular system, this still is not enough to avoid getting real-time peaks if Hyper-Threading is active and SPAN GUI is also showing. However, replacing SPAN with TDR Nova (only for the spectrum analyzer part in full screen mode) really does the trick. It seems that Nova is less demanding on the CPU when displaying its analyzer.

im confused is it better to have asio guard enabled or disabled?reason why im asking is im getting advice not too use it because it causes audio glitches but some say its better performance if i do use it.

also how do i tell if i have hype threding enabled or disabled?i never got a reply before from steinberg when i asked.

heres my system info–
intel core i7-5820k-3.30ghz
32gb ram
windows 10

does system virtual memory paging help ?ive just checked and my computer is set at 2048mb total paging for all drives and thats way below the recommended 4978mb size.i was wondering if this could affect cubase performance.

also will setting my computer to adjust for best performance be much better?i had it set too let windows choose whats best for my computer thing ive noticed is the graphics are less clear when set to best performance…any help


There´s no need to have virtual memory(just stresses drive and taxes cpu), if you have plenty of RAM. 16gb is enough, even 8gb

Jari Junttila…really…i dident know that. I usually let windows decides this. Maybe i should take away this viritual memory then?

As far as I know it’s better not to touch these settings and let Windows manage it.

Fabio and other Steinberg mods/devs: Any idea whether or not this might make a difference in an upcoming version of Windows 10?

“New Windows 10 update enables you to load “potentially thousands” of plugins in your DAW”

Seems like this won’t have anything to do with the MMCSS issues but at least the FLS plugin limit will be lifted, right?

There are two different problems:

FLS (Local Fiber Storage).
The next Windows Functional Upgrade will allow for about 4000 slots instead of a maximum of 128 slots.
Each plugin occupies at least one slot, but there are plugins that occupy more than four slots.

The problem of Windows 10 MMCSS (Multimedia Library).
The library has been moved from user mode to kernel mode as of Windows 10. This now limits the maximum number of virtual processors. The library is currently stable under Windows 10 Version 1809 only if the CPU has a maximum of about 14 logical processors or no more than 32 threads are occupied by MMCSS.

The second problem is not solved by the new and better FLS.
Although there should be a registration patch from Steinberg, but unfortunately the solution is only available on request and not publicly.

What Cubase 10 I do not know exactly, apparently, the program now ensures that a maximum of 32 threads are opened by MMCSS.
In my opinion, this is at the expense of performance. As long as Microsoft does not increase the maximum number of threads runs Cubase 10 with the handbrake on. (Is anyone of a different opinion?) That would mean that the performance of a 20-core CPU from Cubase when using the MMCSS only as a CPU running with 14 logical cores.

The registry patch might solve the problem, but apparently there are people who can not successfully apply the patch:

Thanks for your POV – after more research, I agree, the MMCSS issue of Cubase on Win 10 does not appear as though it will be helped by the upcoming FLS improvements of Win 10, which will mainly just benefit plugin count. But I am curious if Steinberg thinks otherwise.

As for performance improvements with the new MMCSS approach with Cubase 10, in my experience there IS a performance improvement on a 10-core (20-thread) CPU with Cubase 10 over Cubase 9.5, but more importantly the dropout/engine behavior seems improved as well. Unless I missed a bunch of posts, it seems this thread has plenty of examples of people with improvements, so I think whatever Steinberg did with MMCSS management has helped more than hurt, although there are certainly people facing issues that need to be tracked down and solved. Overall, I think it’s a step in the right direction, but I’m sure further improvements are needed.

My understanding is that the old registry tweaks, etc., are no longer needed… at least in my case they’re not needed anymore, but perhaps Fabio can enlighten us on the latest info? He mentioned various switches to control spawning prefetch threads in different ways, etc… wondering if there has been any further intel on further improvements?