VST plug-in failed to load: (80004002)

[altoricky]

Greetings one and all.

I'm using CBB version 2024.07 (Build 108, 64 bit) which I installed back in July. This afternoon I loaded up a project which has been in progress, on and off, for some time and I was informed that the VST 3 reverb plug-in 'Eventide SP2016' failed to load: (80004002). It also fails to load in any other existing project or a new project. In all I have 5 Eventide fx plug-ins and 4 of them display this problem. One of them (Ultra Channel) works fine. They all work fine in Sonar X3. Clearly there's something that Cakewalk has taken a sudden dislike to that doesn't bother Sonar X3.

Before I resort to uninstalling and re-installing plug-ins and/or Cakewalk, I was wondering if anyone might have some helpful insight they could share.

Thanks

Richard

[DeeringAmps]

Have you updated Eventide lately?

Sounds to me like the .vst3 (the plugin itself) is in a folder with .vst3 extension in the folder name. But this was fixed in CbB awhile back. Is 2024.7 the latest version?

not in front of my computer. 
update CbB band run the vst scan…

t

[steve@baselines.com]

I've noticed problems with Kontakt based instruments.  Both Credona Strings and Session Horns Pro caused troubles.  I had to reinstall.  I'm also now having a problem loading up CBB.  It's minor, it says something is running in the background and then when I accept the message it loads anyway.

 

 

[altoricky]

59 minutes ago, DeeringAmps said:

Have you updated Eventide lately?

Sounds to me like the .vst3 (the plugin itself) is in a folder with .vst3 extension in the folder name. But this was fixed in CbB awhile back. Is 2024.7 the latest version?

not in front of my computer. 
update CbB band run the vst scan…

t

Thanks for your comments. Everything is up to date.  I've just downloaded and reinstalled all the Eventide plug-ins but the problem persists. Looking at when I last worked on this project, there have been a couple of Windows updates since then so I may have to roll them back just to eliminate that possibility.

[DeeringAmps]

Check the file structure where the .vst3 is located. If it’s in a folder that’s “xxx”.vst3 then there’s the problem. CbB didn’t like that. Again, not in front of my computer. If 2024.7 is not the latest CbB that’s the problem. If it is the latest CbB update, we’ll I can’t help ya…

[Wookiee]

@altoricky try a rest and rescan. Steinberg thought it be really great to change the "where are VSTa's stored" rules by adding the requirement to a directory with .VST3 on the end so.

Where say it would have been;

Program files/common files/VST3/joessuperinstrument

as the top level directory for the plugin, it has now got to be;

Program files/common files/VST3/Joessuperinstrument.vst3

as the top level directory for the plugin.

[DeeringAmps]

@altoricky What @Wookiee said above.

2024.07 is the latest release and I would have thought that it should deal with .vst3 folder properly.
This popped up first with ToneX for me (and others, there are a couple of threads...).
At first, we were dealing with it by removing the ."vst3" from the folder name.
Then Sonar was updated to "deal" with it. I think CbB had been updated as well...
But, you have to run the vst scan!

Preferences>VST Scan>Manual Scan>Scan
If that doesn't work, then same path but choose Reset... as Wookie said above.

HTH,

t

[Glenn Stanton]

it's the VST3 fault, not CbB nor Sonar. the removing the .vst3 folder extension is a workaround for a faulty implementation of the VST3. i have probabyl 6 or 7 which needed this "fix", but then after the dev folks were alerted to the issue (and likely from any number of people), most of them updated correctly and now work fine with the .vst3 extension on the folder.

[Wookiee]

I believe the scanner has been updated to account for this issue, however it would be wise to report to support as a precautionary measure.