I’ve posted a problem concerning CPU load balancing about a year ago but unfortunately never got a proper solution:
when using multiple instances of the same plugin, agressive mode is a proper way to reduce cpu load. Latest example: NI Symphony Series String Endamble. Arranging 4 instances of kontakt (violins, violas, celli, basses) inside a rack makes a good string ensamble available for live use.
The problem: when calling up this rack cpu loads of 100% and more maxing out the cpu and of course leading to crackles (agressive mode active). A quick look into task manager shows the reason: all instances share the same cpu core!
What I found meanwhile: restarting the engine in agressive mode forces cantabile to use all cpu cores resulting in a maximum cpu load of about 35-40% even when using auto divisi, portamento,…
As I don’t expext a solution inside cantabile in near future my idea is to restart the engine a short time after a song using the strings rack was loaded by using a binding.
Unfortunately every attempt led to a process restarting the engine again and again in cycles (f.e.: source: song - on load -> target: engine - restart). Even a delay didn’t get me rid of the behavior. Obviously the restart process also restarts the binding, restarting the engine,…
So: I’d be very happy for any idea on this workaround.
Thanks and kind regards, humphrey