• SONAR
  • Aud.Ini ThreadSchedulingModel Value
2012/11/12 05:27:26
dlesaux
Hello Friends! Has anyone tried modifying the value of the ThreadSchedulingModel in the Aud.Ini file? I have an i5 processor which is a quad core and I was wondering if this would help balance the cores.  Hoping the Bakers could chime in!
2012/11/12 05:40:28
wizard71
I think it's pretty much a given that it needs to be set to 2 for quad core +
2012/11/12 11:01:37
Jyri T.
From tech sup: ThreadSchedulingModel= Integer 1 This variable goes in the [Wave] section and controls the interaction of the main audio thread and worker threads on multiprocessor systems when the Use Multiprocessing Engine option is enabled. Depending on the system, a particular model may result in less glitching and better overall performance. The values are as follows: 0 = Same as previous versions of SONAR. 1 = (default) Better thread balance. Model is more efficient and can provide cycles for other tasks. 2 = Additional worker thread is created. This may result in improvement with Quad processor systems or higher. Not recommended for Dual processor systems.
2012/11/12 12:07:24
dlesaux
Thanks for the replies! I was wondering because until now, I've never modified any setting in the Aud.ini file and I've always been reluctant to do so.  After changing the value to 2 though, now I get 4 cores working when using Ozone 5 when before it was only a single core (Ozone customer support stated that Ozone didn't support multicore processors!)
2012/11/12 18:11:43
gswitz
Being a dork, I just tried using 1 vs 2 for me on my dual core and I saw a 1:50 seconds to bounce a track for both settings.
2012/11/12 22:30:15
tomixornot
gswitz


Being a dork, I just tried using 1 vs 2 for me on my dual core and I saw a 1:50 seconds to bounce a track for both settings.

You will probably not find speed improvement. But if your project is heavy and the main core is peaking, then this setting will help to distribute all cores more evenly.
2012/11/12 23:34:46
noynekker
dlesaux


Thanks for the replies! I was wondering because until now, I've never modified any setting in the Aud.ini file and I've always been reluctant to do so.  After changing the value to 2 though, now I get 4 cores working when using Ozone 5 when before it was only a single core (Ozone customer support stated that Ozone didn't support multicore processors!)


When I went to the config file to check which value I had for "ThreadSchedulingModel" I noticed mine was already set to 2.
So , leads me to believe this is a default value when you install Sonar 64 bit on a quad core ?

Also, I have a project using Ozone 5 plugin, and notice that the first core shows a heavy CPU load, but if I bypass Ozone 5, all cores have a more balanced load. Surprising, to me, that Ozone would't support multicore processors.
2012/11/12 23:57:49
sharke
I changed mine to "2" recently and have to admit I did see a little bit of an improvement, although the first core is still way more loaded than the others. But this has got to be down to it being used for Windows. I think we sometimes forget that behind Sonar, there is an OS running!
2012/11/13 02:27:42
Teds_Studio
noynekker


dlesaux


Thanks for the replies! I was wondering because until now, I've never modified any setting in the Aud.ini file and I've always been reluctant to do so.  After changing the value to 2 though, now I get 4 cores working when using Ozone 5 when before it was only a single core (Ozone customer support stated that Ozone didn't support multicore processors!)


When I went to the config file to check which value I had for "ThreadSchedulingModel" I noticed mine was already set to 2.
So , leads me to believe this is a default value when you install Sonar 64 bit on a quad core ?

Also, I have a project using Ozone 5 plugin, and notice that the first core shows a heavy CPU load, but if I bypass Ozone 5, all cores have a more balanced load. Surprising, to me, that Ozone would't support multicore processors.

I have an i7 2600k and mine was default at 1.  Just changed it to 2 today and could see a visual difference on the core display.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account