Had a bad time yesterday dealing with Project Corrupted after having updated two Air Music Technology plugins… Hybrid 3 and theRiser
I noticed that there was a 2024 update for both plugins so I did it and right after that, any project in Cubase (14 Pro) having an instance of Hybrid or theRiser were corrupted.
I couldn’t save the project or save a new version of it. I thought I had lost the concerned projects… fortunately after several unsuccessful attempts like importing tracks from other project, deactivate third party plugins and so on… I downgraded the two plugins to it’s penultimate versions… and it worked as before
The sad thing is I had no issues at all loading projects in Reaper with the updated plugins but unfortunately not with Cubase…
What would you have done or what would you do ?
The way I see it is, I stay like that and I can still work in the few projects having instances of those plugins or I do the update and I forget and can’t work in those projects anymore ?
If you can reliably reproduce that behavior with the updated versions (e.g. in a completely new, empty project with just those plugins inserted), I would open a ticket with the plugin vendor.
It is a bit weird though that disabling third-party plugins didn’t solve the issue…
Well, I meant that disabling third party plugins didn’t solve the issue because even if it could help to see the concerned plugin, which I already figured it out before doing that, it could not fix anyway the problem itself right ?
I thought about getting in touch with Air Music Tech but how is that I don’t have the issue with the same plugins in Reaper for instance ? Wouldn’t that be more related with Cubase then ?
DAW handle plugins differently, and plugins also can handle DAWs differently, then there can be other weird stuff involved. It is not that uncommon that e.g. one plugin in a specific version crashes one DAW but not the other.
Whether your exact problem is caused by Cubase or by the plugin is hard to say without access to them, but seeing that the downgrade fixed your problems and this forum isn’t full of reports that projects get corrupted by this or that plugin, I’d say the likelyhood is high that in this case it is some change that Air made in the new plugin versions…
maybe updating your cubase to v14.0.40 will solve it … if they did updates that means there where bugs that needed to be fixed … maybe that is one of them ?
I am not even sure that doing the last update would not make things getting worse in general… Don’t want to take the risk to loose almost finished projects in C14 as I would start new projects only in C15.
I’ve had issues with Air plugins, and in particular TheRiser in the past. Most recently I also did an update on the plugins after bumping problems.
Unfortunately I can’t remember the sequence of events or how I resolved it, but ultimately here on Cubase 15 Pro / Windows 11 TheRiser is working fine. I removed the rest of the Air plugins, so I can’t speak for Hybrid.
Nice plugins when they work, but over the years they have been a real PITA.
Well I never experienced real issues with those plugins before except maybe with theRiser which sometime wasn’t triggering the effect. So I had to ducplicate the track and delete the 1st one, then it worked again like magic.
The thing is, it was only projects with already instances of Hybrid or theRiser that got corrupted. I haven’t noticed issue if I created a new project with an instance of one or the other last updated plugins…
I haven’t tried with C15 as I was affraid of getting more issues than with C14
If I remember correctly, when I made the update, I did not installed the VST2 version. Could this be part of the issue ? If someone would be able to see something in the Dump file above…
I stopped using VST2 plugins after Cubase decided to drop support. It neatly coincided with a PC rebuild I needed at the time. If memory serves, I think Air were a bit slow at moving their plugs to VST3, and I didn’t have them installed for a long while. I bounced all my instances in the main projects to audio (and still use some of those as audio samples now and again)
tbh TheRiser is the only one of their instruments (or FX) that can’t be easily replaced by another similar plugin, which is why I have persevered with it.
I was thinking this when I read your OP. Steinberg dropped support for VST2. So my thought was that you probably used VST2 in the original project and could try to install updated VS2 versions… or go back to the original VST2 versions
I did several tries, doing downgrade then update again, in parallel on my laptop to not risk to lost my work on my desktop.
I noticed that after doing the update that introduces the VST3 version, in Cubase, I cannot see the VST2 version anymore… VST2 is enabled in the Plug-in manager but I only see the VST3 version, altough the paths of the VST2 locations are still there…
I also checked the blocklist… nothing…
This is weird because, in Reaper, I can still see and open both VST2 and VST3 version of the plugins ??
So, unless somebody here or at Air Music can help, I will have to check every project and render the instrument track that have Hybrid or theRiser to Audio and delete the instrument tracks to avoid having the “Project corruted” of the death mess…
@Martin.Jirsak , could you please check the Dump file and share your feedback ?
That is not weird, that is just how Cubase works. If the VST3 version is programmed in such a way that it can automatically replace the VST2 version (which not all plugins are.), Cubase will just show the VST3 version.
