It bears mention again, as I’ve posted somewhere else, and I think Frits mentioned it too once — WHEN PODIUM IS SCANNING MULTIPLE VST PLUGINS:
As in when you are building your database for the first time or making significant changes, IF Podium has just scanned a rather complicated dynamic library — and as you know, some plugins are insanely simple while others are truly massive — the very next plugin after scanning something complex will often get kicked to the Quarantine File, no matter what it is. Podium may falsely accuse the plug of performing an illegal operation, etc. Or perhaps it is just one of those dodgy, older SynthEdit VSTs that will work fine in 99% of cases but has some ‘rough edges’ to its GUI or design.
No matter — Open Up the Quarantine text file, delete the rejected plugin, Save the .txt file, close it, and load the plugin again afterward. I think of it this way: If I were Podium, I’d get tired piling in some of these more massive DLLs and their ‘stuff’ too.
I have used Podium to test more than 200 plugins of every sort imaginable at this point. I think in all that time there were two that were No Go and another one or two I’ve read about. Overall, one of Podium’s greatest strengths, to me, is how it works with plugins and their respective presets. Podium’s dealings with certain plugins’ presets is not perfect in all ways — and I expect before long the system will be modified slightly — yet at the same time it allows for some unique options in handling or creating presets that other DAWs are completely blind to process. I’d greater prefer, I think, having all presets simply show up in the inspector automatically and with no extra fuss anytime I put any plugin into focus, but at least I am able to build or import a library. Some DAWs, I believe, still will have none of this business. I’ve read so many threads elsewhere that are all about “Where are my stinking presets?!” or “My DAW can’t find my plugin’s native preset folder no matter what I try!”
.