Hi Shane,
Since VST2 is pretty much phased out & VST3 is the new standard, wouldn't it be better to remove the VST2 plugins and keep the VST3 plugins?
Also, it would be nice to have a Scan all AU, VST, & VST3 plugins.
I have quite a few plugins that are AU only and it takes me sometime to go through them to figure out which ones they are. It would save so much time to scan every plugin on my computer and then remove the redundant ones while keeping the VST3s.
Thanks,
robo
Since VST2 is pretty much phased out & VST3 is the new standard, wouldn't it be better to remove the VST2 plugins and keep the VST3 plugins?
Inside Unify, VST3 does not provide any advantage whatsoever over VST2. We favor the VST2 format whenever available, because
- It tends to have fewer compatibility issues, and
- It usually results in slightly smaller (sometimes MUCH smaller) saved patches.
Also, it would be nice to have a Scan all AU, VST, & VST3 plugins.
I'll add that to the to-do list, but since scanning is so slow, we recommend only doing it once, and thereafter, adding plug-ins to Unify's Known Plug-Ins list manually.
I have quite a few plugins that are AU only and it takes me sometime to go through them to figure out which ones they are. It would save so much time to scan every plugin on my computer and then remove the redundant ones while keeping the VST3s.
That is pretty much what the "remove redundant plug-ins" function does. For every plug-in in the Known Plug-Ins list:
- If only AU is present, it will be kept.
- If VST3 and AU are present, the VST3 will be kept, and the AU removed from the list.
- If VST, VST3, and AU are present, only the VST will be kept.
If you insist on using only VST3-format third-party plug-ins, you're free to do so; just don't bother scanning for new VST2s. The only cases where you must use a VST2 plug-in are:
- Where there is no VST3 version, and
- To use a "Unified" patch library which has been prepared using the VST version of the plug-in.
Thanks for your explanation Shane!
I wasn't aware that VST3 is so different. I use VST2 right now, which works great. In the near future there won't be anymore VST2. I just thought it would be prudent to start converting over to VST3, so I wouldn't have to re-build all my Unify patches with VST3s.
I guess I'm always adding a lot of new plugins, because my standard procedure is to scan all AUs, VSTs, & VST3s, and then trim out the redundant plugins. I usually start the scan and go do something else while it's scanning, which is faster than me remembering which new plugins I added. lol! As it is now, I have to manually start it 3 times for each format, so a "scan all plugins" would be very handy.
I also wasn't aware how the "remove redundant plugins" command worked. I did search for it in the manual, btw.
It all makes much more sense now. 👍 Thanks for your time !!! 😀
All the best,
robosax
In the near future there won't be anymore VST2.
It's a bit more complicated than that. Anyone who signed a license for the VST SDK with Steinberg prior to October 2018 can continue to create and distribute VST2 plug-ins and hosts forever, and will do so for as long as there is demand. Anyone who signed after that is limited to VST3 only, and that's why you are seeing a lot of newer companies and open-source projects providing new plug-ins in VST3, AU, and AAX formats only.
Steinberg has been trying to force it down the industry's throat since 2008, and the industry's response has been less than enthusiastic. The VST3 spec has changes that are significant enough to require substantial re-design of DAWs and other plug-in hosts. Steinberg redesigned their hosts (of course), and even removed VST2 support this year, but honestly, no one else cares.
I also wasn't aware how the "remove redundant plugins" command worked. I did search for it in the manual, btw.
A search for "redundant" in the manual finds this, which is perhaps a bit terse, but says the same thing:
-
Remove “redundant” plug-ins: Attempts to remove extra versions of plug-ins as follows:
-
Remove VST3 versions of every plug-in for which a plain VST version exists.
-
On a Mac, first remove Audio-Unit versions of any plug-in for which a VST or VST3 version exists.
-
If you have a lot of plugins managing them can be a pain. I've found several tools that help.
PlugInfo from ThinkerSnacks - https://www.thinkersnacks.com/as-pluginfo.html is a quick and useful tool to see and sort all your plugins in all formats. With easy locating of specify plugins in the Finder, ability to sort and filter by name, publisher, type, architecture, version, date and size it has helped me clean up my Apple Silicon Mac of old 32 bit and intel plugins. Oh, did I mention its free?!
If you use Logic and wonder which of your projects use nonworking, demo, outdated or plugins you just want to get rid of I found a solution to search all Logic projects within a folder by using Keyboard Maestro and a script you can download from the Keyboard Maestro form - https://forum.keyboardmaestro.com/t/logic-pro-search-projects-for-plugins-in-the-finder/30672
And just a short rant on plugin installers - I've found Plugin-Alliance's installer to be the best of all the many ones I use - fast, succinct and configurable. Why does every plugin manufacturer's installer need to run a process in background that reports back to mother? I'm ok with uploading my plugin list when you use the installer so the installer knows what I have but don't suck up my CPU and clutter my system just so you can monitor me.
Hope this helps
Thanks,
K Light
Thanks for the explanation, however there seems to be a glaring issue with all the U-He presets. Since quite a while now U-He no longer supports VST2. So I can't get any of the U-He presets to work on my new MacBook, even though I have them all installed as VST3.
Are there any plans to at least update the "broken" U-He presets so us newer users, who don't have redundant U-He VST2 installers lying around, can get these to work?
Thanks 🙂
...there seems to be a glaring issue with all the U-He presets. Since quite a while now U-He no longer supports VST2. So I can't get any of the U-He presets to work on my new MacBook, even though I have them all installed as VST3.
Are there any plans to at least update the "broken" U-He presets so us newer users, who don't have redundant U-He VST2 installers lying around, can get these to work?
None of this is my responsibility anymore, but I should mention that you are talking about "unified" patch libraries, which are basically gifts provided to Unify users at no charge. Updating them can therefore not be prioritized as highly as, say, fixing bugs.
I'd suggest you post requests for updated unified libraries in the Unified Libraries & PlugIns - Official Instructions + Sign Up section of the forum, where there are a number of users with time and ability to do this work.
Yes - Unified libraries for particular plugins are basically just a convenience in terms of being able to list all the factory patches of a particular plugin directly inside the Unify patch browser. I don't have time to go through this process but others have done it and shared the resultant libraries with PluginGuru - and those are made available on the website.
I'm not aware of any automated way to do it in the past - maybe Shane had some custom tools - I forgot honestly - it's been quite a while since I discussed this with Shane.
When it comes to specific PluginGuru libraries that are developed for a specific synth plugin, if those need to be updated to support VST3 due to the plugin developer no longer supporting the VST2 version of their product, we must contact the original library author to ask them if they can help to update it (and provide a version for download to John to update the downloads page at PluginGuru.com).
I had a chat with Fred Nongat at Synthfest France and he mentioned his son had been working on a AI generated patch conversion tool that might be able to convert Unify libraries with the specific plugins he uses (e.g. Diva) - I guess it works for specific cases in translating from VST to VST3, because each plugin may have a different arrangement/mapping of parameters that you can't apply a universal conversion tool to (and the storage formats of VST and VST3 are very different).
One thing to add.. anybody making new Unified libraries or libraries that require a specific plugin should use VST3 now when saving patches, since then we can ensure the library will work on Mac OS as well as Windows (which would not be the case if you saved presets using the AU version of the hosted plugins - since that's not available in Windows).
Thanks a bunch for these replies. It makes total sense now :).
