If this is even possible at all, I speculate that one or both of these approaches might work. outlined below. I'm looking for any helpful guidance, either in support of the method(s) below or advice to the contrary. Thanks !
- Using embedded VCS layouts, where a PresetSpace might be used locally for each embedded layout, with each maintaining its own local list of presets. I'd use this approach if I was sure about how to divide up the parameter space into N groups of M:n parameters each.
- Using a Multigrid, where any track is either used to generate and send control data, or to receive and interpret control data to modify its audio signal before output. I'd use this approach if I wanted to experiment more with controlling different groups of parameters in real time.
If a track is used to generate and send control data, it might accomplish it by either:
- sharing parameters by name across tracks by explicitly setting this behavior using the popup menus.
- using sounds that receive and output audio for both kinds of tracks. The tracks that are acting as receivers of control data will process any incoming audio that is routed from another multigrid track, by using a STGC or related module, to generate control data for subsequent local processing. Since a receiver sound should be able to receive perhaps up to nine individual control data sources (by using, say three PresetSpace modules, each controlling three indivdual parameters), could this be achieved by using a multitrack audio input?
- using sounds that "output control data" (?) instead of audio, and then by making sure that any sound on the receiver/audio tracks is "made to receive" one or more controller sources*
- I haven't been able to figure out yet how to create individual Kyma sounds that can accept a controller input from the output of another Multgrid track. The only way I can think that this might be possible is by encapsulating the signal flow of the entire sound within its own custom class, that expects one or more green ?variables as input.