Hello,
I have trouble with VST3 replacement mecanism; which is not implemented i guess because my VST2 are still seen as Spire-1.5 and not replaced by Spire.
Can VST3 replacement functionality be implemented in Spire (so i could go on cubase 14 with no trouble) ?
https://steinbergmedia.github.io/vst3_d ... +VST2.html
VST3 (automatic) replacement mecanism
-
- KVRist
- 488 posts since 10 May, 2009
Hi!
Spire supports manual migration from VST2 to VST3:
1. Duplicate your VST2 Spire track.
2. Replace the VST2 instance with VST3 on the duplicate track.
3. Save the preset from the VST2 track to your library.
4. Load the saved preset into the VST3 Spire instance.
5. Recreate any automation, if necessary.
If you have questions or need assistance, please contact support@reveal-sound.com.
Spire supports manual migration from VST2 to VST3:
1. Duplicate your VST2 Spire track.
2. Replace the VST2 instance with VST3 on the duplicate track.
3. Save the preset from the VST2 track to your library.
4. Load the saved preset into the VST3 Spire instance.
5. Recreate any automation, if necessary.
If you have questions or need assistance, please contact support@reveal-sound.com.
-
- KVRer
- Topic Starter
- 14 posts since 25 Dec, 2009
Hello,
Thank you for the workaround, i had it in mind.
But cubase 14 won't let you do that as you can't load VST2 anymore, and i don't want to switch back each time.
Thank you for the workaround, i had it in mind.
But cubase 14 won't let you do that as you can't load VST2 anymore, and i don't want to switch back each time.
-
- KVRAF
- 37396 posts since 14 Sep, 2002 from In teh net
This would be much better.shamk wrote: Sat Nov 16, 2024 10:28 pm Hello,
I have trouble with VST3 replacement mecanism; which is not implemented i guess because my VST2 are still seen as Spire-1.5 and not replaced by Spire.
Can VST3 replacement functionality be implemented in Spire (so i could go on cubase 14 with no trouble) ?
https://steinbergmedia.github.io/vst3_d ... +VST2.html
-
- KVRist
- 488 posts since 10 May, 2009
Hi!
The manual migration process we mentioned earlier remains the only available method.
-
- KVRist
- 488 posts since 10 May, 2009
We understand the inconvenience, but please note that the decision to drop VST2 support in Cubase is not something plugin developers control.
Currently, Spire does not support automatic VST2-to-VST3 replacement, and we recommend using the manual migration process as outlined earlier. This approach is still the only available method at this time.
We appreciate your understanding.
Currently, Spire does not support automatic VST2-to-VST3 replacement, and we recommend using the manual migration process as outlined earlier. This approach is still the only available method at this time.
We appreciate your understanding.
-
- KVRAF
- 14439 posts since 16 Feb, 2005 from Planet Earth, Somewhere
Yes, indeed the vst2 dropping in Cubase is beyond the plugin developers control, but the vst2-vst3 is completely within your control.
Fortunately I don't have many projects that I actually used Spire in.
rsp
Fortunately I don't have many projects that I actually used Spire in.
rsp
sound sculptist
-
- KVRAF
- 37396 posts since 14 Sep, 2002 from In teh net
Maybe but migration is part of the VST3 spec and there are several ways to implement itvega555 wrote: Sun Apr 06, 2025 12:42 pm We understand the inconvenience, but please note that the decision to drop VST2 support in Cubase is not something plugin developers control.
-
- KVRer
- Topic Starter
- 14 posts since 25 Dec, 2009
Additional information regarding this issue:
Cubase 15 starts correctly under Rosetta, but it crashes almost every time I select a track containing a Spire instance.
Older projects can only be opened under Rosetta because they contain the VST2 version of Spire. However, since Cubase crashes when I select those tracks, I cannot open the Spire interface, save the preset, replace the instance with Spire VST3, or properly migrate the project.
When I start Cubase with all third-party plug-ins disabled, the projects open normally.
This strongly suggests that the crash is triggered when Cubase tries to access or initialize the Spire instance under Rosetta.
As a result, these projects currently cannot be migrated manually from Spire VST2 to Spire VST3.
Cubase 15 starts correctly under Rosetta, but it crashes almost every time I select a track containing a Spire instance.
Older projects can only be opened under Rosetta because they contain the VST2 version of Spire. However, since Cubase crashes when I select those tracks, I cannot open the Spire interface, save the preset, replace the instance with Spire VST3, or properly migrate the project.
When I start Cubase with all third-party plug-ins disabled, the projects open normally.
This strongly suggests that the crash is triggered when Cubase tries to access or initialize the Spire instance under Rosetta.
As a result, these projects currently cannot be migrated manually from Spire VST2 to Spire VST3.