Sorry I’m confused. My plugin is using the managed parameters system but with AudioProcessorParameter and not AudioProcessorParameterWithID.
So when i read the code right, i have to use the macro, because the behavior in the wrappers looks like completely different from what they do in the previous version also when using AudioProcessorParameter instead of AudioProcessorParameterWithID
Edit:
Further explanation, it looks like with AudioProcessorParameter, there will be a hash generated from the parameter number, so this is completly different
You should be using this macro if you have already released plug-ins to the public using AudioProcessorParameterWithID or AudioProcessorValueTreeState before this fix was done. This is because the IDs of both classes was not reported to the host.
So this is also true if my plugin uses AudioProcessorParameter (if yes, your post was bit misleading )