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

Hi everyone,

with Cubase 10, the way resources are addressed and used changed in order to overcome the much discussed MMCSS limitation and generally improve performance on high core-count machines.

If you have a CPU with 16 or more logical cores and have already updated, it would be great if you could could give us a short feedback: a post here, a mail to support (with a ‘FW to Fabio’) or a PM to me are all fine. Of course, any changes you applied ( file, disabling HT or registry key) need to be reversed before checking this out - this could affect previous versions of Cubase installed on the same system [edit: more details here Cubase 10, Windows 10 and multi-core (14+ cores) - Cubase - Steinberg Forums]. Please do that only when time allows and NOT if you are on a tight schedule.

To those who were already in contact with me for trouble-shooting, analysis, tweaking, etc.: I’ll soon get back to you, I’m in the process of checking my cases and collect data.

Thank you!

What is the best way to back out the previous fix? 6950x processor here. Thanks.

I have been using JBridge to work around the MMCSS limitation. Is there still a limit or just an improvement? Do I still need to use JBridge at this point?

How to roll back the fixes:

If you applied the Registry Key: follow the previous instructions to find the key you have created, select it, right-click and delete the key.
→ Remember: I can’t post it here :wink:

If you used the file: you don’t need to do anything, it is saved in the previos version’s preferences, and it still needs it.

Those who preferred to disable hyper-threading may want to re-enable it.

The MMCSS limitation exists of course, but the audio engine spawns threads in a very different way and should not affect Cubase. I say ‘should’ because on a limited amount of configurations issues may still be experienced. Way to long and complicated for a post, but if the issue kicks in, it is possible to improve, if not fix it completely. Those having MMCSS-related performance issues with Pro 10 should contact support.
The issue should be no more in the majority of cases, though - meaning undoing the fixes were needed is the only thing one needs to do.

Is Cubase 10 compatible with Intel Turbo Boost?

Turbo Boost is a motherboard / CPU feature, so Cubase is not ‘compatible’ or ‘not compatible’. As long as it works fine with the other system modules / features, Cubase will use the power available. I’m personally keep it enabled since Intel Gen.3 and only disable it for trouble-shooting (users’ cases) and testing.

Please, keep this on topic - I posted this to collect specific data about MMCSS. Thank you.

OK, many thanks and sorry for going off topic

Is multi-thread performance also supposed to be enhanced in windows 7 ?

(title of thread has me thinking otherwise)

Thank you, Fabio, I look forward to testing Cubase 10’s new multi-core/thread improvements. You’ve been very helpful about the prior issues, which is very much appreciated! Will report back when I get a chance to test it!

Yes, multi-core performance is a general improvement.

I specified Win 10 because the MMCSS limitation does not affect operation on Win 7, 8 and 8.1 - previous references can be found here:

Oh, and thanks, uarte!

Hi. 20 cores 40 threads here! I thank the team for the excellent work. There are performance improvements. ASIO meter now works without spikes and clicks.

can you pm me how to reverse what I used for Cubase 9.5.
in the previous version I had pops and clicks and very poor asio it was great for ages then a windows update and future Cubase update totally screwed everything up so I was advised to use the registry edit and the cmd edit.

my computer spec is—

windows 10 build 1803
intel core i7-5820k @3.30ghz
32gb ram
audio interface-- uad apollo twin usb

also what options within cubase 10 do you recommend i use ?do u use steinberg power scheme…etc ?

Just installed Cubase 10 on my 10-core (20-thread) on Win 10. First impression is that the new multi-threading model is indeed better! Will be playing with it more, but this is starting out positively for me. Hope these improvements will make it over to Nuendo soon too.

I just re-enabled hyperthreading on my 12-core i9 7920X and will be doing some testing. :slight_smile:

I’m on an i9 7940 (14 core 28 thread) and Cubase 10 is working great. I removed the registry fix and I’m able to turn on Hyper-threading which lets me have more plugins on my master channel and more headroom before maxing out the system. Awesome!

I haven’t tried playing with the Steinberg Power Scheme but I’m curious if it would help. Anyone have any idea about AVX BIOS settings and what is optimal for Cubase 10?

Buying a CPU with Cubase 10 in mind. would users think an intel 8700k (i7) or 9900K i9) would perform better? Is the i9 worth the leap?
I intend to buy on black Friday

ZeroZero, replied to this via PM. Can we please keep this thread about feedback? Thanks a lot - feel free to start a thread in the Computer Setup, perhaps some users have that CPU already!

i7800k cpu… speedstepping and turbo mode enabled, but C states still disabled just incase, 32 gig ram… multiprocessing enabled along with asio guard. ive been able to reduce buffer sizes to lower latency and all seems good so far, no pops or clips.
i was expecting to see te audio performance meter drop a bit. i assuming there is no link between internall processing and the meter… just thought there would be a show???.

Fabio (and interested others), I’m posting a link to a new thread I started regrading Windows 7 64bit and my issues with very problematic multi core usage of my 6950x (10 core) and Cubase 10. Cubase 9.5 worked perfectly.

Just some feedback - I have an 8 core HT 7820X o/c to static 4.3ghz in W10 Pro. On paper my performance should have increased 12.5% in a jump from 7 cores to 8, and in practice I think that’s pretty plausible. I have one especially intensive project laden with hungry soft synths that used to break up on AG2 set to low in C9, thus far it’s played it fine in C10 - just. The meters are still very high, so it’s not a massive difference, but I’ll take every single .1% of that 12.5% improvement! So from my perspective - fixed, and thanks.