New way of adding parameters to AudioProcessorValueTreeState not sufficient for many, identical parameters

[t0m]

If you use your own RangedAudioParameter subclass then you can do whatever modifications you wish. The difficulty is propagating this information via the plug-in SDKs to the host. For example, parameter name changes have only just become possible via the VST3 SDK (and are not yet supported by JUCE):

VST3 parameter name changes don't work

There is a problem in the VST3 wrapper, that prevents parameter name changes to be propagated to the host. The VST parameter table is created in setupParameters, but they are never updated. Any plugin that changes their parameter names after load will not work properly with this.

With dynamic parameter ranges you may have differing levels of success in different hosts and formats.