Using a VST3 plugin, the MIDI CC parameters that we have mapped show up as automatable parameters. That is happening because StudioOne ignores the fact that some parameters are listed as non-automatable, which we already knew.
But WHY are all of these parameters created at all? They are created in initialiseMidiControllerMappings(), along with storing mappings in an array.
In VST3 (without JUCE), all you have to do to get MIDI CCs mapped to existing parameters is to implement getMidiControllerAssignment() in the effect component, returning the desired mappings. That function is there, but it draws from the array created in initialiseMidiControllerMappings(), rahter than allowing us to respond with our own mappings.
Why are all these parameters created? Why can’t we just implement getMidiControllerAssignment() with the mappings we care about?