Hi!
I have the same issue with old projects using Hybrid after I updated to latest version.
My workaround is to
Try that to see if it works!
Regards
/Hackej
Yeah I believe you are right about it is how Cubase works… and I think it is a pity it works that way…
I have checked with Reaper, no issues, all my projects are safe. The existing projects still runs the VST2 and I can also load the VST3 from the last update beside that.
I already lost several tracks within projects in the past in Cubase after I made the update of Halion were I used Transverse…
Thanks @Hackej for your workaround.
I was also thinking doing the same but I first need to evaluate how many projects with how many instances of theRiser and Hybrid I have.
The thing is, I can’t just do it like this as I have designed most of the effects or sounds within the projects.
The way I see it, I will rather do one of the 3 options below
Uncheck the Auto-save box in Preferences, then:
Option 3 will clearly be the fastest solution. Risers are risers, you design it, use it and move to another one. With synth sound design it is a bit more delicate, you might want or need to use it again…
I also received a strong support from Air Music Tech that was honestly unexpected. They really want to help.
As this could help others I will let people know what I did at the end
Would anyone knows if it’s possible to prevent Cubase 14 Pro to open the VST3 version of a plugin where it was initially loaded with a VST2 version (making a critical error and project corrupted) ?? Or at least temporarelly ?
@Martin.Jirsak Do you know something about that ?
Thanks for any help
As I wrote previously: if you have installed Air plugins with VST2 and VST3 then go to the VST3 folder, move Air plugins from it to some other location and then you can open Cubase and work with VST2. Then save presets, remove instruments from tracks, save projects and close Cubase. Finally restore VST3 plugins into their valid location, open Cubase and re-apply all instruments again to all your projects.
This at least helped me to overcome this problem.
Yeah you’re right, but what I wanted to achieve was to be able to load the VST2 with tracks having initially the VST2 while also be able to load the VST3 in a new track.
I have noticed that, unless I just render all instrument tracks, I could not for instance simply load the VST3 in place of the VST2 as I would lost all the automations of the track by changing its plugin…
It’s a tricky situation and a lot of work… I have, at least, a few huge projects were I would like to continue working with…
I also tries to copy/paste the Plugin Setting from the top right Cubase plugin window, but it’s really messy. It does only copy the same preset of the plugin but not its parameters…
If the VST3 is programmed in such a way that it can automatically replace the VST2 version, it is not possible.
I assume it is not as projects with VST2 still loads without any issue with Reaper. It’s a Cubase thing
Then you have to use Reaper if that is so important to you. In Cubase it works as I described, there is no way around it. It’s a design decision Steinberg made because their plan was to supersede VST2.
What you mean I have to use Reaper ?
It only concerns open projects. I have nothing against switching to VST3 only, it’s just that, I would like Cubase sometime to be more kind of open or flexible, like for instance, Reaper…
It’s a design decision, I understand… I would just like to be able to do the switch safely in a smoother way than having critical error messages that freeze everything and make the project corrupted and stuck
Just as an aside, you do wonder how one plugin can do so much damage.
Just tried importing tracks from a 2024 project, one of them TheRiser, and not only did I get the ‘your project is corrupted’ series of messsages from Cubase all related to TheRiser, but Windows 11 gave me a huge message on screen about a serious problem ocurring and promptly rebooted.
About time to let TheRiser go along with the other Air products methinks …
Why would you do that? Honestly, they are great plugins.
As it as been said above, this is more about Cubase behaviour with VST2/VST3 plugins, but with Air plugins.
I have no issues at all with any projects in Reaper… only Cubase…
It as also been confirmed with Level II Tech support from Air Music who assisted me on the otherside with this issue. They have been great. Greater than many support teams.
If you want to load your old track, I suggest to you to use the proposed lifesaver tip form @gitarul , temporarily move the vst3 files so Cubase open the vst2. It works.
One thing also to mention is that Air Music Tech has freed themself from iLok system ! They now have their own InMusic center software. They would deserve to be used only for that 
A similar issue happened to me with Lexicon plugins. I had some old project with their VST2 loaded previous version. On a new computer I’ve installed the new VST3 so then opening the project Cubase was warning about missing plugins. I had to open the project on the old machine, copying individual plugin settings with a screenshot (you can save them but the VST3 can’t read them). All of this because I’ve got rid of all VST2.
So, to summarize, here are two workaround that works:
Temporarily moving the VST3 files from C:\Program Files\Common Files\VST3 to another folder allows Cubase loading the projects without errors as it will load the VST2 instances of the plugins. Allowing you to render the Instrument tracks to Audio tracks, for instance. Or see option 2
After moving the VST3 files and opening a project that had VST2, you can hot swap the VST3 files again in C:\Program Files\Common Files\VST3, re-scan the plugins in the VST Plugin Manager. Then you will have your project with VST2 instances and you will be able to also create new tracks were VST3 instances will be loaded and manually copy all the parameters from the old track having the VST2 to the new track having VST3.
Simply loading again the VST3 version of the plugin in the track that has the VST2 version will make you loose all the automations that you might had in this track…
After doing one of the two options, old tracks with VST2 instances must be removed otherwise an error will occur again when you will re-open a project in Cubase.
Hope that helps