How to get Studio One to recognize I un-installed a plugin

[madFloyd]

Googling leads me to the old forum, lol.

Help! I'm working with Softube to try and understand why the VST3 version of Console 1 no longer works and part of the process is removing every trace of it on my system and re-installing but Studio One still thinks it's installed.

Thanks!

 

[lokeyfly]

You could re run scan at startup in the Options/VST Plugins tab during a fresh startup. Reopen Studio one and check. If your plugin is still visible, you'll need to open the plugin manager, remove it, and reset the blocklist there. Then close and reopen open Studio One again. If you deleted the plugin outside of Studio One, make sure it was properly removed. Studio One doesn't know this until plugins have been re scanned upon opening and set to do so.

Be sure to turn off re scan plugins afterwards to shorten startup time.

 

[madFloyd]

You could re run scan at startup in the Options/VST Plugins tab during a fresh startup. Reopen Studio one and check. If your plugin is still visible, you'll need to open the plugin manager, remove it, and reset the blocklist there. Then close and reopen open Studio One again. If you deleted the plugin outside of Studio One, make sure it was properly removed. Studio One doesn't know this until plugins have been re scanned upon opening and set to do so.

Be sure to turn off re scan plugins afterwards to shorten startup time.

Appreciate the reply!

The VSTs are indeed gone from my hard drive, but re-scanning plugins inside Studio One doesn't remove them.

And I do not see a way in the plugin manager to remove plugins.

I wonder if the only way is to 'Remove Plugin Settings' and start from scratch....?

 

[lokeyfly]

Been a while, but I believe it's reset blocklist.That worked for me.

 

[madFloyd]

Been a while, but I believe it's reset blocklist.That worked for me.

I didn't try that, because I had no blocklist content, so don't know if would have worked, but my guess is that it wouldn't.

What did work was to remove plugin settings. I'm guessing this is not just locations of plugins but the actual 'database'.

Anyhow, something was wrong or corrupt in there because un-installing the plugin and re-installing it (i.e. replacing the VST 3 dll file) didn't produce results (I'd drag the plugin to a track and S1 would act as if it were trying to load it - and then nothing). Eliminating the VST from the database and re-scanning worked.

I need to remember this the next time I have this type of issue (this wasn't the first time).

 

[Vocalpoint]

What did work was to remove plugin settings. I'm guessing this is not just locations of plugins but the actual 'database'.

This is the way.

Even tho Presonus did finally give Plugin Manager some love in v7.2 - they still have not clued in (after many years) on how to make Plugin Manager realize that a specific plugin has been uninstalled.

The plugin startup scanner mechanism seems to do nothing in this case. What it should do is realize that a plugin that WAS there last startup - is now not here this startup and remove it from the DB on the fly.

But until those smarts are addressed - the best we can do is a full destroy and rebuild of the plugin DB.

VP

 

[madFloyd]

This is the way.

Even tho Presonus did finally give Plugin Manager some love in v7.2 - they still have not clued in (after many years) on how to make Plugin Manager realize that a specific plugin has been uninstalled.

The plugin startup scanner mechanism seems to do nothing in this case. What it should do is realize that a plugin that WAS there last startup - is know not here this startup and remove it from the DB on the fly.

But until those smarts are addressed - the best we can do is a full destroy and rebuild of the plugin DB.

VP

Well said. My (movie) media player recognizes when a file is removed just as easily as it recognizes a new addition. I'm sure it's not that difficult, just hasn't been made a priority.

 

[lokeyfly]

Even tho Presonus did finally give Plugin Manager some love in v7.2 - they still have not clued in (after many years) on how to make Plugin Manager realize that a specific plugin has been uninstalled.

The plugin startup scanner mechanism seems to do nothing in this case. What it should do is realize that a plugin that WAS there last startup - is now not here this startup and remove it from the DB on the fly.

But until those smarts are addressed - the best we can do is a full destroy and rebuild of the plugin DB.

VP

Ah, I see that. Thanks for noting Vocalpoint. Probably best to refer back in the days before PM and simply delete (fully) the plugin. If necessary, change its location of that path if it isn't used any longer in the Studio One VST locations. Then perform the scan at startup. Then close, and startup. Even that seems like a lot of overkill, but its always been the case. I agree with VP, the plugin manager should detect a change from the scan at startup routine. They should be tied together in some uniform way.

 

[Djaii]

I've been trying to figure out what files are modified when I use "Remove Plug-In Settings" because it seems like an option might be to directly edit THAT file to remove anything (assuming it's in some type of human readable format like XML or json). I assume using the remove function destroys a bunch of stuff I'd like to keep (like my folders organizing all the plugins the way I like and the thumbnails). I'm loathe to do that, or test it, since I wouldn't know what file to restore after to undo it.

Can anybody shed a little light on this before I just blow the plugin db away?

 

[lokeyfly]

As I recall, VP is correct. So even modifying plugins and performing a plugin db clear in the Plugin manager would best rebuild itself. No difference as the plugin manager simply doesnt compare a simple plugin startup rescan. Mind you thats from the plugin manager only. Any presets you saved within each plugin isn't removed. The plugin manager rebuild simply sees what plugin is no longer present. So if you had a preset for example saved from Plugin Alliance Amek 9099 for a ducked bass guitar setting, and you never removed it. Then it's not because the Studio One Plugin Manager was swiped and rebuilt that will discard those preset settings. Still, I'm not certain that every preset held within Studio One's own presets, they would dissappear. I dont believe so, judging by my still in place presets all over the place. Meaning track presets, favorites, etc.
Other's mileage may vary.

 

[Vocalpoint]

Just delete the db and carry on. Not a lot of value in wondering what this does.

I have been deleting the db since 2011 and have never seen this effect anything but making sure the plugins you do want - are correct in the system.

VP

 

[Djaii]

Fair enough.