VST Connect 5.5.10 Maintenance Update now available

Dear all,

today we have released the 5.5.10 maintenance update for VST Connect Pro/SE and Performer. We recommend all users to download and install the update as it fixes some issues and comes with improvements.

A full list of all the fixes and improvements can be found in the version history, available in the SDA and on these websites:

VST Connect SE/PRO Downloads

VST Connect Performer Downloads

2 Likes

Great update, thank you :slight_smile:

Hi all!

Am I the only one having a very hard time just lauching the VST Connect Performer program with this new update? Software crashes and process is killed on startup, caused by VST2 plugin scanning. Very unstable when scanning plugins, and tried to find the culprit plugins, by adding one by one, but they are way too many to be caused by plugin devs.

To be able to open the program, need to empty the whole VST2 plugin folder of its contents. Now once VST Connect Performer is open, I am able to get to the Settings, try to uncheck the VST2 Plugin check box in the Plugin Manager tab, but everytime the program simply crashes and shuts down.

Spent several hours trying to make it work but gave up. For these reasons, this update is unusable for me at this time if clients have the same problem opening the software on their side :frowning: Sad person I am!

Edit: Forgot to mention, I’m on Windows 10 x64, latest updates, trying to make sure VST Connect PERFORMER works on my side before shooting to clients.

There are situations like this with every other VST host, mostly because some plugins violate the VST protocol. In this case, one has to narrow the culprit, usually best starting with free or otherwise ‘suspicious’ plugs, if that doesn’t nail it, remove 50%, still crashing? We then know it is within those 50%, so then remove half of it again until you found it. This ‘sucessive approximation’ method involves only few steps even with a massive load of plugins.

Also, you may want to examine this folder:
C:\Users\myname\AppData\Roaming\Steinberg\VST Connect Performer_64
(where you have to replace “myname” with your win user name). In there, you will find a file ‘Vst2Plugins.xml’, open it in a text editor and search for “damaged” and “valid”, this might show you where to find the culprit. There is also ‘Vst3plugins.xml’ for VST 3 plugins. Good luck!

2 Likes

Thanks for the tips @musicullum . I finally renamed my VST2 plugins folder, then managed to get VST Connect Performer running, went to the Settings and changed the VST2 folder location to an empty folder I created, and then closed the program and renamed my VST2 plugins folder to its orginial name. This now allows VST Connect Performer to start smoothly by actually not loading any VST2 plugins but only my VST3 plugins.

It’s the equivalent of simply unchecking the VST2 Plugins check box inside VST Connect Performer’s Settings, to “disable” the loading of VST2 plugins, just that trying to uncheck the said box actually crashes the program every single time on my side.

Thanks so much for your help and time with this issue!

Cheers,

Thanks a lot for the update. We would still be interested to learn which plugin causes the problem, so if you don’t mind we’d appreciate if you could send us said Vst2Plugins.xml file. Then we can possibly save other users the trouble. Thanks!