Is there a way to see how many computer cores Dorico is using? With just string section my 3.4Gz/ 32Gb ram with 12 cores is overloading. Even with hefty EW samples this does not seem right.
Thanks, Ron
Not AFAIK. Best way to control that is VEPro where you specify the number of cores to be used. Dorico doesn’t handle big orchestras too well in my experience, best to offload that to VEPro.
I’ve got, what 14/28 cores? Works great with this configuration.
Hi @roncleave , first of all, are you on Win or Mac? I presume you are on Win, right?
In that case, Task Manager can show you how much processing is going on on each core, but not in detail for which app it is doing something.
Is your concern that Dorico is working too hard on just one or few cores while leaving the others idling?
Least to say, the Dorico audio engine always tries to distribute the load to as many cores as possible, in order to equalize out the performance, but there are many more variables in the system that have an impact on the core usage.
But also audio drivers can have a big impact on the performance. If you go to Edit > Device Setup, what driver is chosen there and at what sample rate is chosen? And if you click on the Control Panel button, a new window opens, what sample buffer size does it show?
Hi Ulf. I am using a Mac. (driver- core audio) sample rate- 44100, buffer- 256 With Haleon all is well. With EW Opus…
not so great. Thanks for your effort. Ron
Hi Ron, if all is well with HALion then I would blame Opus for the bad performance.
Maybe it is not optimized for multi-core usage. I don:t know Opus well enough to say something,
but try to fiddle with the settings within Opus and see if you get some better results.
HALion for example has a switch where you can specify the number of cores to use at the same time. Maybe Opus has something similar…
Opus has settings for minimum medium, or maximum multi-core usage, as well as the extent to which it will preload samples. They do make a significant difference. I had an issue with Opus just today. I very much respect its capabilities, but Opus will find any weakness your system has.
Yes, in my experience with Opus 32 GB of memory is easy to run out of with just strings if you aren’t really disciplined and limited in articulations and such - and you don’t run Opus because you wanted the same sample sound on every note, you know? 64GB memory can get tight, and it doesn’t take a large orchestra to get there.
Do watch out that Opus wants by default to put a separate new instance of convolution reverb on each and every instrument by default, so make use of the master reverb feature in Opus to keep things like that down a bit. This is a good reason to put all strings in the same vst instance for example so that they can share.
I think it is actually pretty well behaved, but it lulls me into forgetting how abrupt it can be when it does fail. Like driving on a scenic mountain road maybe 
1 Like
Thanks Gregory, I set it to Max and presto! all is well. Now if I could just find out why Dorico keeps showing the pinwheel and dragging it’s
heels. Ron
Maybe you should not max out for Opus and thus leave some air to breathe for Dorico 
2 Likes
I’ve found “half the available cores” to be a useful rule of thumb