...on an 8 core CPU with CPU parking disabled, why does the first core seem to carry most all the load and, when it gets too high, start bogging down with clicks and pops...while those other seven numbnuts are just lolly-gagging around doin almost nothin????
 
Jim Roseberry...or anyone else...hip me, will ya?
 

That could be a software development. Some things are not design for multicore. Is the result the same with parking enabled?
 

Olpal,
 
Anytime there is a GUI involved, the process reverts to core 1, where the main interface thread resides, by default.
 
In general, if you have a project that starts bogging down with multi-timbral VSTi's, and you aren't ready to "print" track audio, you can try opening another instance of the VSTi and move some tracks from the old instance to the new instance. Most VSTi's dont do multi-core processing very well, and each instance will land on a core and stay there.
 
Back to my original point, when you open a project with lots of VST's, they will spread around pretty well if you've told Sonar to allow it (see http://forum.cakewalk.com...e-CPUs-m2095428.aspx). Once you start opening the VST GUi's though, core 1 will start to load up. So, save, close and reopen the project to spread stuff around again.
 
Regards,
Dan
 
 

Hi Olpal,
 
As has been mentioned

• The GUI runs on one core
• Numerous plugins aren't optimized for use with multiple cores

 
You can try to mitigate the glitches/dropouts by using larger buffer sizes... but (of course) that increases latency.
 
Under Preferences>Audio>Configuration File, try changing the ThreadSchedulingModel parameter to "2".
 

Thanks Dan and Jim!!  Will try all your suggestions.  Trouble is on some projects I'm already at maximum buffer size.  The downside of some of these newer "do everything" plugs I'm loving is they are all CPU hogs.  Dern it.
 
PS:  And I know it's time for me to upgrade my Studio Cat in a major way Jim, ol pal.  I'm trying to find a way to do just that.  Will keep you posted:-)
 
And @Dan...I'm getting a Server Error when clicking on your link.  Can you repost it?
 
 
 

Never mind Dan...I figured it out.  Turns out...natch...I already had set the setting to "2".  
 
BUT...since this is a GUI thang...would a newer super fast video card with more memory on it help in any meaningful way??
 
 

yorolpal
Never mind Dan...I figured it out.  Turns out...natch...I already had set the setting to "2".  
 
BUT...since this is a GUI thang...would a newer super fast video card with more memory on it help in any meaningful way??
 
 

Glad you sorted it. I was about to repost the link. And no, a video card won't make any difference, and may actually cause other problems due to the way some graphics cards hog the PCI bus.
 
Regards,
Dan

This was an excellent thread!! Thanks to YPO for asking, and the responses. 
 
Can I ask a question of clarification to make sure I'm understanding correctly:
Rather than have one VSTi with eight instruments, it would be more efficient to have four with two each (or two with four each)?  Have I got that right?
 
Thanks!!

jude77
This was an excellent thread!! Thanks to YPO for asking, and the responses. 
 
Can I ask a question of clarification to make sure I'm understanding correctly:
Rather than have one VSTi with eight instruments, it would be more efficient to have four with two each (or two with four each)?  Have I got that right?
 
Thanks!!

It depends entirely on the VST you are using. All I can say is, try it and see. I've had good luck doing this with EastWest's Play and Omnisphere, less so with Kontakt, which is already pretty efficient.
 
Another very important thing to do is to not store your samples on the same drive as your projects. I've also found that it can be necessary to separate types of samples from others just to spread the load out onto more than one sample drive. Or just get a big ass SSD...
 
Regards,
Dan
 

Thank you very much!!