VST3 IPluginCompatibility

Audio Plugins
1

Hi,

I wonder if there is an official list of VST3 hosts that support IPluginCompatibility (that is, if plugin “Foo” says in its moduleinfo.json that it can replace plugin “Bar” , the hosts that support IPluginCompatibility will load Foo in projects that use Bar , when Bar is not available). In JUCE plugins, this compatibility info is published with the JUCE_VST3_COMPATIBLE_CLASSES macro.

And then, among those hosts, which of them do implement the “CompatibleParametersIds” (if Bar parameter “blipblop” had a VST3 id of “42” in Bar, and “1042” in Foo, then this allows the host to not break its automation curves when Bar is replaced by Foo)

Obviously, Cubase implements that, but is it the only one ?

It is not directly a JUCE question, since this is a VST3 feature implemented by JUCE it would be interesting to know.

Also: I know that there is something similar for AU ( kAudioUnitMigrateProperty_FromPlugIn ), but I don’t think there is support for parameter id compatibility.

2

Not to the best of my knowledge.

I think Native Instruments wanted to support this too in order to transition a host of theirs to VST3. I can’t recall which product though. Komplete Kontrol maybe?

However, I’ve noticed some other DAWs take a different approach. The main issue being solved is for transitioning VST2 plugins to VST3. Reaper for example seems to manage the migration as long as you add the same parameters in the same order (but they don’t need the same IDs), this is probably the case for most plugins, but it would cause issues if the manufacturer ever wanted to change parameter order, remove a parameter, or add a new parameter in the middle of the existing ones.

TBH I haven’t looked into that.