Yes @t0m noticed this a few days back. We can fix this in JUCE but then all automation data of currently available JUCE plug-ins would become invalid if plug-in vendors update their JUCE version.
We would probably need to introduce yet another preprocessor define to force JUCE to use the current param IDs and - in absence of this define (for new projects) - only use values which are lower than 0x7fff. Just dumb that we already have a preprocessor define which does something very similar JUCE_USE_FORCE_LEGACY_PARAM_IDS.
To be honest this seems like a Studio One bug to me.