In the latest version of my script, I abandoned the mapping process of plugins (except from the EQ and pregain). So, now, exactly as you say, multiple CCs trigger the same (duplicate param). I don’t know exactly the internal handling but it works fine, at least so it seems. (Perhaps it duplicates the step of change but I haven’t noticed something bad)
Very good suggestion! I have another one as a feature-request about the type of the param to bind to. To me, it’s much better to bind a button to a button and so on.
https://forums.steinberg.net/t/mparameterbankzone-additional-property/831806
Now, if you really want and have the time to map your plugins, I’ll tell you about my initial script:
I was creating a gigaintic paramZone (I was looping through 200+ params with makeParameterValue) as if my controller surface supports this size.
By using in testing the sub
param.mOnTitleChange=function(activeDevice,activeMapping,pluginName,paramName){}
I grabbed every parameter. When finished, I created multiple customVars (200) and I’ve mapped the ones to the parameters I wanted, avoiding duplicates and also, correctly mapping buttons to buttons and so on.
However, I worried about the consistency of so many params getting handled and this is the reason I abandoned it, apart from the possibility of the plugin’s creator, changing params.
If you think you want to try this approach, I can share the code, no problem 