I came across this, when setting up some instruments with layers to fake unison voices. The hit on the CPU was shockingly heavy, already for a few voices. The sample routing in instruments seems to be quite inefficient, when different samples of an instrument share a common modulation set. I’d consider this a concept bug.
At the moment it appears, each sample is processed seperately by the applied modulation set. In case of samples sharing the same modulation set that’s completely redundant. It should be way more performant, to process the summary of the raw samples a single time by the modulation set. That in addition would mean, the “send to FX” currently applied in the sample settings becomes a global setting for all samples sharing the same modulation set. The routing of every single sample hereby becomes obsolete too. The only signal remaining to route to FX would be the one-time-processed result of the modulation set. That actually should result in an another massive performance boost.
The processing of filters, filter modulation for each voice is the main bottleneck here, the other modulation and FX sending is not really relevant in this case. We can try optimizing the filters a bit more, but this can then only speed-up the processing of simultaneously triggered samples.
I had it already deleted, when I wrote the origin posting, because it was just useless that way. You know I’m usually someone providing things. I wouldn’t have any problem to set this up again in the old system, but I really don’t feel like doing this in 3.0 again, because the bad workflow for editing a bit complexer sounds is really just annoying. This ain’t no diva behavior or something like that. I’m just really getting upset, when I have to work with the current “solution”.