Questions & Answers

Why does every version of Studio One after 4.5.0. crash when opening certain plugins and certain song files?

+1 vote
asked Dec 10, 2019 in Studio One 4 by jawan095 (310 points)
Everytime I download a new update after 4.5.0. Studio One always crashes on certain Plugins and certain songs. You guys must've added something to every update after 4.5.0. that crashes Studio One regularly.

3 Answers

0 votes
answered Dec 11, 2019 by kevincollins1 (910 points)
I'm having a similar issue with VST3 plugins and instruments. When selecting and loading Studio One hangs for minutes.
0 votes
answered Dec 11, 2019 by robertgray3 (38,700 points)
Some song files get corrupted. Create a new song file and use “Import Song Data” to import everything from the old file. It’s mostly painless.

If you’re asking “why do song files get corrupted” no clue, there could be tons of reasons, with all the 3rd party software I’m using I doubt anyone could ever figure it out definitively. Support just tells people to use Import Song Data when it does happen.
0 votes
answered Mar 11, 2020 by fransvannispen (4,500 points)
I have had this dozens of times, and found where the problem lies. It happens with plugins of which both a VST2 and VST3 version are installed, and which are not coded to be different. Both VST2 and VST3 in these cases use the same name and same ID.

The advantage is, that when you used a VST3 and remove it, it will load the VST2 version. But somehow, S1 mixes the codebases resulting in random crashes. Mainly at opening a project.

Simple solution is to remove the VST3 version of these double plugins. They are easy to find, as in the plugin manager, there is only a VST3 version shown of these. The VST2 version is hidden because it's aliased/mirrored by the VST3 version.

The VST plugins that work correctly and have no issues in S1 show up in the plugin manager as both VST2 and VST3 version. But if you used the VST3 version and remove it in this case, it will not find the plugin as the VST2 has a different ID and hence is not the same plugin.

If you have removed any double VST2 or VST3, you need to remove the plugin config and do a full scan, as they are cached.