Too bad about this one, but this brings to mind the nature of hardware samplers - in particular a machine like the original TX, and that's Templates. You could painstakingly set up general mappings for different purposes (drums, octave splits, ect) then use a common Exernal CC or Host Automation parameter to control the same modulation in for all the samples. This workaround would have shortcomings obviously, but if your template is designed well you'd just load it up and replace the samples (maybe even have blank placeholders in the groups instead of actual samples). I think the factor here would be to use the same CC/Automation throughout assigned to the same modulation. Lots of work but could be feasible?lalo wrote:I'd like to have a global filter / envelope / LFO etc. section at the program level. So it would be possible to modify globally some parameters for all the groups/split/samples
I'm going to experiment with this one. Filtereing all the samples in a drum kit for instance is a normal enough effect.

