VST2 ot VST3 migration stratgy

Developer VST 3 SDK
1

Hi,

I have developed a plugin that has been in the field for some time and offers VST2 and VST3 variants. Cubase shows the following UIDS:

VST2: 56535430613669746274656368206365
VST3: F2AEE70D00DE4F4E5442504154423739

I now ask what the best strategy is to migrate from VST2 to VST3 in case that a project is opened with VST2 and VST2 is no longer available:

  1. VST2: effVendorSpecific
  2. VST3: IPluginCompatibility
  3. VST3: Moduleinfo.json

Thanks for any help.

Best
Thomas
TBProaudio

2

Hi,
Have you had a chance to check out this page: Compatibility with VST 2.x or VST 1 - VST 3 Developer Portal

Feel free to come back if something is not answered there.

3

Thank you for yur prompt support.

I implemented IPluginCompatibility, which works pretty well with Cubase and Studio One.
And I implemented vendorSpecific as well, to support Reaper.

But now I have the problem that Cubase makes an auto conversion VST2toVST3 even if the VST2 plugin is still there.
How can this be?

4

OK, found out that is a Reaper thing.
Reaper supports IPluginCompatibility as well, so no need for vendorSpecific.

Thank you for the support!