Hey guys. Is there going to be multicore support for Diva in Logic on the new macs (M1 and above)?
I remember there was a discussion around the M1 launch time and tldr was it couldn't be done or needed more time or something to that effect. Is that abandonware now? I haven't heard much about it since. Thanks.
Diva multicore in Logic
-
- KVRist
- 176 posts since 20 May, 2014
-
- u-he
- 30188 posts since 8 Aug, 2002 from Berlin
On Apple silicon it is better to run Diva without the Multicore option.
When it's on, some voices are going to be rendered on efficiency cores, which are something like 4x slower than performance cores. The main core running the engine may then have to wait for such voice to finish, and that wait can cause a drop out. Unfortunately we can neither detect what type of core the software runs on, nor can we practically force to be scheduled on a certain type of core.
With Multicore off, Diva is very likely going to run on a performance core, which should have enough juice to handle her.
When it's on, some voices are going to be rendered on efficiency cores, which are something like 4x slower than performance cores. The main core running the engine may then have to wait for such voice to finish, and that wait can cause a drop out. Unfortunately we can neither detect what type of core the software runs on, nor can we practically force to be scheduled on a certain type of core.
With Multicore off, Diva is very likely going to run on a performance core, which should have enough juice to handle her.
-
- KVRian
- 695 posts since 9 Dec, 2021
I think Diva multicore should be on by default on Windows though. Till this day I still see content creators that dont know about the option and say Diva is high CPU.Urs wrote: Wed Oct 22, 2025 6:06 am On Apple silicon it is better to run Diva without the Multicore option.
When it's on, some voices are going to be rendered on efficiency cores, which are something like 4x slower than performance cores. The main core running the engine may then have to wait for such voice to finish, and that wait can cause a drop out. Unfortunately we can neither detect what type of core the software runs on, nor can we practically force to be scheduled on a certain type of core.
With Multicore off, Diva is very likely going to run on a performance core, which should have enough juice to handle her.
-
- u-he
- 30188 posts since 8 Aug, 2002 from Berlin
Unfortunately (or not), some of the latest and greatest CPU to run Windows on have efficiency cores, too. I'd highly advise to keep MC off by default.
As for content creators, if they are not expert enough to know what they talk about, I mean... ouch. We do live in the worst possible timeline. Anything for a click, right, as long as it doesn't involve reading the user guide.
As for content creators, if they are not expert enough to know what they talk about, I mean... ouch. We do live in the worst possible timeline. Anything for a click, right, as long as it doesn't involve reading the user guide.
-
- KVRist
- Topic Starter
- 176 posts since 20 May, 2014
Okay thanks. But the feature works great in CLAP format. How is that different? Reason I ask is I can't quite move to Bitwig entirely. I use Ableton and Logic primarily (and moving ever so slowly away from Logic and towards Ableton fully) so I guess the question could be extended to Ableton too not just Logic. It's not always an issue but there are quite a few patches here and there that struggle a bit while working just fine with Multicore enabled in Bitwig. Stacks are the worst offenders I guess off the top of my head.
-
- u-he
- 30188 posts since 8 Aug, 2002 from Berlin
So, yes, CLAP. You're right. With Bitwig it totally makes sense. Apparently, if the number of threads is reasonably low (like, the DAW maintains the threads for the plug-ins), it's manageable to stay on performance cores (I don't know exactly how Bitwig do it, but in my observation it's 100% performance cores for plug-ins). So with CLAP and Bitwig, Diva lets the host schedule its threads, and that's where this works pretty well.
If everyone supported and used CLAP and its thread pool extension - as people should, really - we'd immediately make this a default setting.
That said, I've just worked on preferences, maybe we can add one for Multicore and see how it works out... and maybe we can make it so that different plug-in formats can have different prefs.
If everyone supported and used CLAP and its thread pool extension - as people should, really - we'd immediately make this a default setting.
That said, I've just worked on preferences, maybe we can add one for Multicore and see how it works out... and maybe we can make it so that different plug-in formats can have different prefs.