1
Icarus / Re: FR: Allow Icarus 3 vst3 to substitute Icarus 2 vst2
« Last post by Markus Krause on April 30, 2024, 08:44:05 AM »An automatic substitution of VST2 to VST3 is highly problematic for complex plugins. Both plugin formats are technically very different and have a significantly different feature set. e.g. VST3 does not offer full MIDI support. As a result automation and Midi parameters might not get mapped correctly and songs might be messed up or sound different.
I will run some tests, but I am not optimistic that an automatic migration will work properly for all possible scenarios.
You can use 'Open with Rosetta' if you want to work on an old project. The Intel version of Cubase supports VST2.
https://helpcenter.steinberg.de/hc/en-us/articles/4488195658002-Cubase-12-Nuendo-12-Using-the-native-Apple-silicon-version
Or you can migrate your tracks by using 'Open with Rosetta'. Then you could render/bounce the vst2 tracks. Then save the song. Then disable 'Open with Rosetta'.
Please note: It is technically possible to run VST2 on M1 native. Other DAWs on the Mac support it. It's purely Steinberg's own decision to drop downward compatibility for VST2 on M1 Mac.
Markus
I will run some tests, but I am not optimistic that an automatic migration will work properly for all possible scenarios.
You can use 'Open with Rosetta' if you want to work on an old project. The Intel version of Cubase supports VST2.
https://helpcenter.steinberg.de/hc/en-us/articles/4488195658002-Cubase-12-Nuendo-12-Using-the-native-Apple-silicon-version
Or you can migrate your tracks by using 'Open with Rosetta'. Then you could render/bounce the vst2 tracks. Then save the song. Then disable 'Open with Rosetta'.
Please note: It is technically possible to run VST2 on M1 native. Other DAWs on the Mac support it. It's purely Steinberg's own decision to drop downward compatibility for VST2 on M1 Mac.
Markus