I have just bought a new machine which has more cores, but I'm not sure what the optimum setting will be for the number of audio processor threads parameter:
http://www.mutools.com/info/docs/mulab/audio-setup.html
I understand that it could be wise to leave one core spare to handle the UI, but I don't fully understand how the vsts that do multi-threading should be handled. I'm assuming they will need their own cores that are not used by MuLab? So for instance, if you have 6 cores you could give Mulab 3, leaving 1 for the UI and 2 for multi-threading vsts? Also, I'm not even sure which of my vsts are multi-threading. Would leaving 2 cores for them be too many?
If anyone could shed any light on this, it would be much appreciated. I appreciate that this setting will be unique for everyone's individual setups.
Number of audio threads setup
-
- KVRist
- 374 posts since 13 Sep, 2011 from UK
-
- KVRist
- Topic Starter
- 374 posts since 13 Sep, 2011 from UK
Since no one has graced this with a response, I guess it must be a dumb question. I'll leave it using the default ( the total number of cores ) and see how it goes. I understand Reaper has intelligence built in to equally distribute load among cores. If MuLab doesn't have this, it would certainly be high on my wishlist.
- KVRian
- 1352 posts since 17 Aug, 2012 from Old Zealand
I think the general rule is that if your cpu have 8 cores you set
MuLab to 7. If 6 cores then 5 and so on.
My cpu is supposed to have 8 cores but only 4 of them are "real"
so I set it to 3 and leave one free for the GUI work.
I could be wrong but I don't think you have to worry about
plugins. That is handled by MuLab or the plugin.
Cheers
MuLab to 7. If 6 cores then 5 and so on.
My cpu is supposed to have 8 cores but only 4 of them are "real"
so I set it to 3 and leave one free for the GUI work.
I could be wrong but I don't think you have to worry about
plugins. That is handled by MuLab or the plugin.
Cheers
-
- KVRist
- Topic Starter
- 374 posts since 13 Sep, 2011 from UK
Thanks for your answer sbj. I think you are correct about the plugins. From what I've read, the host is responsible for distributing them among the cores. One thing I found with my machine is that 3 (out of 6) of the cores were being 'parked' by windows, leaving them idle. This can be changed by tweaking some registry entries. Now I've done that, it's looking good.sbj wrote:I think the general rule is that if your cpu have 8 cores you set
MuLab to 7. If 6 cores then 5 and so on.
My cpu is supposed to have 8 cores but only 4 of them are "real"
so I set it to 3 and leave one free for the GUI work.
I could be wrong but I don't think you have to worry about
plugins. That is handled by MuLab or the plugin.
Cheers
Last edited by mgiambro on Wed Mar 18, 2015 9:39 pm, edited 1 time in total.
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Note that the host has no control over how plugins use multi-core processing. That's another level of complexity in this story. Optimizing for the best results may depend on the used VST plugins. But leaving one real core free for UI work indeed is recommended cfr http://www.mutools.com/info/docs/mulab/audio-setup.html
