More complicated than "it looks like your request for Multi-Core support will not be granted" ? I was just going by what you were saying......Urs wrote: Sun Apr 21, 2019 7:05 pmIt's a lot more complicated than that. Until Repro-5, we always had a strict separation between synths that have multi core support and synths which have a mod matrix. The two concepts were mutually exclusive. The reasons are quite obvious once you know what happens.Teksonik wrote: Sun Apr 21, 2019 6:45 pmAnyway I'm sorry you can't use Hive to its fullest but it looks like your request for Multi-Core support will not be granted so.....good luck. I hope you find a solution.![]()
For Repro-5 we broke that limitation. And if the ModMatrix in Hive was still a simple as the one in Repro, and if the modulation sources were as simple, we could probably enable multicore support within a few minutes. But this isn't the case. The presence of single trigger envelopes and LFOs alone contradicts the concept of multi core support.
I believe that adding multicore support to Hive would open a can of worms. We would have to add a lot of code, like, exceptions and stuff, which most certainly adds more CPU consumption.
Sounded to me like Multi-core support won't be coming to Hive. Why is irrelevant to me....Urs wrote: Sat Apr 20, 2019 11:44 am I think Multicore support would cost more overhead than the benefit would be worth. As long as a single instance is still fully playable I'm sure you're better off letting the host handle the distribution of plug-ins onto CPU cores.
Anyway I don't have a problem with Hive's CPU demand. I find it reasonable even at more extreme settings. I might keep an eye on the CPU meter when using Diva but with Hive it's not something I even worry about......
