> What does this mean? so the particular use-case was for a sampler. we had a bunch of different samples that had their own domain parameters, which needed to

> What does this mean? so the particular use-case was for a sampler. we had a bunch of different samples that had their own domain parameters, which needed to be automatable. hell, even multi-sample sample selection (the process of choosing which samples of a multisampled sample-set to use) was automatable. it was hell.. aha. that said, i envisenged a few other scenarios although they mostly revolve around variable IO (e.g. variable numbers of sidechained inputs, etc.) > I'm way more dubious about genuinely dynamic parameters. you're right to be. the approach i came up with was a conceptually a mess - although i guess it worked - the dynamic portions of automation could be mapped basically the same way that one routes audio in the daw. you have, say, 10 automatable gain parameters visible to the host, then in the plugin you'd route that to your chosen parameter. no joke, there was the question of making the parameter mapping itself automatable. i told them it was impossible and i would die on that hill, which is technically not a lie.