What's new

Question about the way cpus handle VI's

Open Lane

A Strange Bird.
I have a question about my cpu's functionality. From what a gather, not all of the cores (my cpu has 16) are kicked on until needed. In my eastwest software samples I have like 5 or 6 instruments going at the Sametime and the upper right hand corner says the cpu is function at 20%.


As my computer loads more vi's do more cores kick on? If they do, as the number of core usages go up, will the cpu percentage usage tick down?

Or is the 20% number a static number that already displays based on total cores avail and the number will only go up?

If someone could explain this number I'd really appreciate it!

Thanks!
 
Last edited:
I have a question about my cpu's functionality. From what a gather, not all of the cores (my cpu has 16) are kicked on until needed. In my eastwest software samples I have like 5 or 6 instruments going at the Sametime and the upper right hand corner says the cpu is function at 20%.


As my computer loads more vi's do more cores kick on? If they, as the number of core usages go up will the cpu percentage usage tick down?

Of is the 20% number a static number that already displays based on total cores avail and the number will only go up?

If someone could explain this number I'd really appreciate it!

Thanks!
Depending on your CPU, you are 100%, correct, cores get parked until needed. I have an i9-13900KF which is 24 cores / 32 threads, and it did that very thing. LatencyMon after the first minute would bark at me that there were issues with my system that can cause latency. I finally figured out it was the parked cores. And it directly affected Cubase… drove me crazy. So I just turned it off. Now all cores are running and I am one happy camper, lol. Well, there’s mandatory undervolting too, but first, you want all cores running.

Here’s how:
  • Change your Power Scheme to High Performance (click Start and the Gear icon to open Settings; reply if you can’t find where to do that… on an iPad right now typing, can’t look)
  • Type or copy this and hit enter:
    • powercfg /setacvalueindex SCHEME_CURRENT SUB_PROCESSOR CPMINCORES 100
  • Then copy or type this to save it to your current power scheme:
    • powercfg /setactive SCHEME_CURRENT
Then reboot and your cores will be running!

So that is the manual way to do it. If you prefer to have a nice app to do all the above for you, then use ParkControl, which also sets your Power Plan for you:


Once you get that sorted, the other issue if you have a 12th to 14th Gen processor is CPU voltage being too high which makes your CPU throttle down, because the higher voltage makes it hit the 100°C max too quickly. Mobo makers ship settings too high to ensure stability, but for DAW towers it’s not good. Once I adjusted mine down, I can run a cubase project with all threads at 100% and I barely get over 80°C, and that’s on air on a Noctua cooler. The frame I mounted my CPU comes into play too, but that’s not an easy solution, so I’d just concentrate on opening all cores and undervolting.

Here’s a general video on how to do that but try searching for other vids specific to your motherboard so you truly understand it al:

 
Last edited:
If someone could explain this number I'd really appreciate it!
Me too. The good news is it doesn't really matter.

CPU usage indicators are all over the place in terms of what they actually measure and how they measure it. For DAW use they're almost completely meaningless.

All that matters is whether or not you hear pops/crackles/stutters. They can happen at high CPU usage and they can happen at low CPU usage. Note, however, that the only projects I've seen that are actually CPU limited in the last decade are synthetic benchmarks.

If you wind up with a project that is actually CPU limited, post it here and we'll help you figure out what's up.

Until then, just get on with writing music :)

rgames
 
Not an expert but most audio plugins are single threaded (meaning they only use a single core) and the DAW usually decides which cores to use.

Every DAW has a different strategy on how to distribute the load on the CPU cores. Eg: usually all the plugins in the same audio channel go to the same core because sending data between CPU cores has some latency.

Honestly I wouldn't worry about it. Let the machines do their work. This is way too complex and you can't do much about it anyway. It's not like you can say "hey Mr DAW put all these plugins into this core".
 
I have a question about my cpu's functionality. From what a gather, not all of the cores (my cpu has 16) are kicked on until needed. In my eastwest software samples I have like 5 or 6 instruments going at the Sametime and the upper right hand corner says the cpu is function at 20%.


As my computer loads more vi's do more cores kick on? If they do, as the number of core usages go up, will the cpu percentage usage tick down?

Or is the 20% number a static number that already displays based on total cores avail and the number will only go up?

If someone could explain this number I'd really appreciate it!

Thanks!

20% does not mean that 20% of your cores are in use. It means your CPU cores (all of them) are being utilized 20% utilization over all. Meaning they are spending 80% of the time sitting around waiting for something to do.

this may or may not mean that some cores are currently in active.

The way multi-core computers work is a bit more complicated, it's not that all the work of your software automatically gets divided out equally to the cores spreading the load. It doesn't work that way at all, its much more complicated....

core usage is a factor of the software you are running, software can be coded to run different tasks in parallel. Its not always true that tasks be ran in parallel, often times task B requires task A to complete first, so those two tasks can't be executed in parallel, they have to be in series, one after the other. Any software you run will be trying to run things in parallel when its possible. Not everything can. And it's considerably more complex at times to run non-dependent tasks in parallel as well. But this is something that DAW'S generally know how to do when specific tasks can actually be done in parallel. In a very limited simple way we could say, for example, that each mixer channel in your DAW mixer, can be processed in parallel to the other channels, for example, but the plugins within each mixer channel have to be processed in series... The second plugin can't do what it needs to do until the plugin above it has finished, etc. so DAW's are attempting to do things in parallel whenever possible, but not everything can be separated out as parallel tasks. And DAW's are undoubtedely using different multi-threading strategies to maximize parallelism.

In software, a parallel task is called "A thread'. In all the software running on your computer at the same time, including background processes, they each might have one or might have a few or more threads of execution. When there are multiple threads, they are all trying to run in parallel and compete for time on the CPU cores.

All of those threads, basically take turns using the available hardware cores. And if at a certain moment in time, there are not enough active threads to make use of all the cores...then not all the cores will be used for that period of time, until more threads, between all the various software you are using...have enough actually active threads that all the cores will be utilized.

Don' t know if that makes sense, but anyway the bottom line is that 20% usage number you are seeing does not mean 20% of the cores are used, it means that the average usage over the past couple of seconds across all the cores in your system, is only 20% of overall cpu capability, 80% of the time they are sitting there waiting for something to do.
 
Hijacking thread with a related question:

Is it still so that each instance of Kontakt runs in it’s own CPU thread? I.e. so if you’re gonna load 6 articulations, it’s better to use two (or more) instances of Kontakt instead of just one instances?

Because then the work can be distributed between multiple CPU cores.
 
Hijacking thread with a related question:

Is it still so that each instance of Kontakt runs in it’s own CPU thread? I.e. so if you’re gonna load 6 articulations, it’s better to use two (or more) instances of Kontakt instead of just one instances?

Because then the work can be distributed between multiple CPU cores.
Each instance can support multiple cores.
How you balance between multiple instances and multiple cores will depend on your preferred workflow and hardware.

 
Well, you’ll get differences of opinions on the subject, but for Intel processors running windows 10 or 11 AND CUBASE, you have to get all cores running. we have already proved that on here with a lot of testing. It made all the difference in the world on my rig, and it made all the difference in the world on two other another members who built newly identical machines that I did. one is running Nuendo.

If you are running a different DAW, you’ll have to look into that. Audio runs on a single core, but a good DAW can send multiple signals out across all cores, for lack of a better description. Studio One 4 was absolutely atrocious at that which is why I left it in 2019 and went to Cubase. Fortunately, starting with version 5.2, studio one started getting good and now I don’t think it’s an issue at all. So it’s definitely a DAW issue as well.
 
Well, you’ll get differences of opinions on the subject, but for Intel processors running windows 10 or 11 AND CUBASE, you have to get all cores running. we have already proved that on here with a lot of testing. It made all the difference in the world on my rig, and it made all the difference in the world on two other another members who built newly identical machines that I did. one is running Nuendo.

If you are running a different DAW, you’ll have to look into that. Audio runs on a single core, but a good DAW can send multiple signals out across all cores, for lack of a better description. Studio One 4 was absolutely atrocious at that which is why I left it in 2019 and went to Cubase. Fortunately, starting with version 5.2, studio one started getting good and now I don’t think it’s an issue at all. So it’s definitely a DAW issue as well.
Oh, this sounds really interesting.
I followed a video where I was suppose to "disable" most cores and use just one for audio.
Is there a thread or video that explains how you set up the computer and Cubase?
I would really appreciate it.
 
Oh, this sounds really interesting.
I followed a video where I was suppose to "disable" most cores and use just one for audio.
Wow. Plesse don't do that if your DAW utilizes all cores/threads.
Is there a thread or video that explains how you set up the computer and Cubase?
I would really appreciate it.
Oh boy, probably a lot of them, but there are a lot of factors... what CPU and how mucj ram are you running? Which version of Windows and Cubase? Which audio interface? As far as Cubase is concerned, getting all the previous things up to speed is the majority, and then I would definitely turn on ASIO Guard in Cubase, it does the best job of managing audio crackles IMO.
 
Wow. Plesse don't do that if your DAW utilizes all cores/threads.

Oh boy, probably a lot of them, but there are a lot of factors... what CPU and how mucj ram are you running? Which version of Windows and Cubase? Which audio interface? As far as Cubase is concerned, getting all the previous things up to speed is the majority, and then I would definitely turn on ASIO Guard in Cubase, it does the best job of managing audio crackles IMO.
Thank you for the answer @PaulieDC.
Yeah, I have read and watched a lot of videos and tutorials about this, trying to get the best results.
I have an Intel i7-9700KF, 128Gb Ram, Windows 10 Pro version 22H2, Cubase 12 Pro with ASIO guard and multiprocessing activated, Apollo Duo Twin USB. Changed power settings, disabled USB sleep on the computer and so on.
I was hoping I more or less could apply the same settings as you, if you have found the most effective settings. But I realise that every system might have it's own settings and quirks, and that there is a jungle out there. :emoji_disappointed_relieved:
Thanks again for your insights.
 
Thank you for the answer @PaulieDC.
Yeah, I have read and watched a lot of videos and tutorials about this, trying to get the best results.
I have an Intel i7-9700KF, 128Gb Ram, Windows 10 Pro version 22H2, Cubase 12 Pro with ASIO guard and multiprocessing activated, Apollo Duo Twin USB. Changed power settings, disabled USB sleep on the computer and so on.
That all sounds good on the PC side. One last thing but this only applies if you are running an NVidia GPU: Disable HD audio in the BIOS, uninstall the NVidia HD Audio drivers from Apps & Features, and make sure you download the Studio driver from NVidia's site, not the Gaming Driver. When you disable HD Audio on the MB, you DO lose regular PC audio. If you just use the Apollo then you're fine, but if you want PC audio for monitor speakers or some other non-DAW reason, then you'll have to keep it. I say disable it at this point, to remove any variable.
I was hoping I more or less could apply the same settings as you, if you have found the most effective settings. But I realise that every system might have it's own settings and quirks, and that there is a jungle out there. :emoji_disappointed_relieved:
Thanks again for your insights.
Have you run LatencyMon? It's pretty good at revealing the components or drivers that make your PC take a hit. You havnen't mentioned it, so if you haven't, you really need that baseline to try and zero in on this:


Open the app after a clean reboot and within the first 5 minutes you should see the bottom bars (most likely) shoot across, with a description of the issue.
 
Top Bottom