Spire: Feature requests

[LAV888]

We need those envelopes/lfos to react visually to changes in ADSR!

[MrJubbly]

Please do not worry, VST3 support is on the way.

This is good to hear.

Could you please ensure that when you do release your VST3 version, that you also support the requisite internal plugin IDs so that 'automatic migration' from VST2 to VST3 will be possible, such as it is within certain DAWs who support the combining of VST2/VST3 plugins (like FL Studio does).

This will allow users who previously saved projects using the VST2 versions of Spire, to then automatically substitute VST3 instances in place of any existing VST2 versions in previously saved projects.

Several plugin developers currently support such "automatic migration" for VST2 to VST3 such as Valhalla DSP, Sonic Academy, Applied Acoustics Systems'.

I contacted Valhalla to query how they managed to correctly implement this functionality for their plugins within DAWs, whereby many other developers had previously been unable to.

Here was their response (hopefully it may help you find a way to likewise support automatic VST2 to VST3 substitution):

Valhalla DSP Customer Support:

As far as automatic migration, I think that the Valhalla plugins benefitted from migrating to VST3 fairly late (in late 2020, to be precise). I use the Juce framework for my plugins, which a lot of plugin companies do, so porting to VST3 mostly involved hooking up to the latest VST3 SDK, downloading the latest Juce SDK, and enabling the VST3 build option. Which seems simple, but there are a few problems with this:

- The VST3 SDK is constantly changing. Which is weird, as VST3 is supposed to be a “standard.”
- Juce had their own VST2 implementation for several years, which had an incorrect VST Plugin ID generation (the bytes were out of order). So, if a Juce developer was building a VST2 and VST3, even if they supposedly shared the same ID, the DAW may not recognize it as the same ID. Juce has now pulled their VST2 implementation, so more recent builds might address this.
- VST3 plugin support is a shifting entity in DAWs. VST2s tend to work the same across all DAWs, but it is a crapshoot about whether or not the VST3s will behave the same across DAWs.

So, my guess for what is going on with other developers is that

- they name their VST3 builds something different, which is either intentional or accidental
- the VST Plugin ID has different formatting between VST2 and VST3, which is probably accidental.

I’m not sure how to fix the VST Plugin ID issue. I only have one plugin that was affected by this, a build of VintageVerb from 2018 or so. The latest VintageVerb builds match the older VintageVerb builds as far as VST Plugin ID, and the VST2 and VST3 plugin IDs match each other now.

Hopefully this is useful info!

[Marsi]

is there a rough indication of when the Spire VST 3 update will be released ?
Just roughly...
next month ?
next quarter ? ...

[Cogency]

Adding support for MPE would be great to extend the current functionality.