For starters, the issues I'm about to explain were prevalent in version 5.5.1, as well as the latest version 5.5.2.
Issue #1 - Studio One 5 scanning 0 - 10,000 plugins on startup. First of all I don't have 10,000 plugins. Not even close to that. Second, I realize I could disable scanning at startup, but that doesn't fix the issue. A few days ago, out of curiosity, I let Studio One 5 scan all 10K plugins. Took 2.5 hours and multiple times I had to click the "QUIT" button on the same McDSP plugin (Futzbox). I had to do this like 6 times over the span of S1 5 scanning all 10K plugins. LOL. So weird. It's like S1 thinks I have 5-6 copies of the exact same plugin thus it's scanning them multiple times, to add up to 10K in number. Any ideas as to what could be going on or how I could solve this issue?
Things I've tried so far that haven't worked:
- clearing DNS settings
- Uninstalling/ Reinstalling S1 5
- replacing hosts file
- remove plug-in settings within plug-in manager
- resetting blocklist
Things I've made sure are correct
- Preferences-->Locations-->VST Plug-ins
Issue #2 - One particular song shows missing devices (mostly plugins and one instance of Steven Slate's SSD5 Sampler) when they are NOT missing in the plug-ins folders. For example, when I go to a certain AUDIO track that shows a missing FabFilter Pro Q 3 on it, and try to add it again, the new instance shows up...so why wouldn't it just load then when the song loads?? That's a mystery (Chris Farley)!
When going to an INSTRUMENT track though, and reloading Steven Slate's SSD5 Sampler, it does NOT show up. However, if I were to make a new instrument track and load SSD5 on it, SSD5 shows up.
I guess my question for Issue 2 is, would it be plausible to take the song and copy it over to a completely new song file? I don't have the terminology correct here or I'd speak more fluidly. I guess what I'm looking to do is find out if the song has something corrupt within or if its S1 5 in general.
