Notifications
Clear all

Multiple / Double Plugin Versions

4 Posts
2 Users
1 Likes
94 Views
robosax
(@robosax)
Trusted Member
Joined: 3 years ago
Posts: 46
Topic starter  

Posted by: @getdunne

Thank you for the XML file. I'm writing some custom Python code to analyze it, because it's so large. So far I've found only one duplicate, an effect VST called elysia phils cascade. Are you aware of other duplicates I should look for?

You have a lot of Waves plug-ins. Waves is one of very few companies that packages large groups of plug-ins into a single VST or VST3 "shell". This might be affecting Unify's ability to detect duplicate entries (but I doubt it).

Two final thoughts:

  1. We generally advise that you perform full plug-in scans only once, and thereafter, register newly-added plug-ins individually (that's a link to the manual; click the words to follow it), to save time and avoid this kind of issue.
  2. We also advise that you scan fully for VST, VST3, and AU plug-ins once, then use the Remove "redundant" plug-ins item on the Operations menu in the Known Plug-Ins View. This will attempt to remove AU plug-ins for which a VST/VST3 is available, and VST3's for which a VST is available, leaving you with a minimal set of "most compatible" plug-ins. Note this may fail in some cases, when the plug-in name and/or vendor name is not identical for different formats, but it works in at least 90% of cases.

These advices notwithstanding, if you are patient enough to help debug this issue, I'd appreciate it.

Hi Shane,

Have you found a solution to this?

I'm regularly getting multiple versions of plugins.  Since I have so many plugins, something is always getting updated every month.  It would take a long, tedious time to remove the doubles.

So every month (or more), I have to Clear all plugins, scan VST, then scan VST3, then remove redundant.

The version numbers are listed in the Description column.  Can you add a Remove older versions command?

Or how about a command that does all 4 steps in one command, so I can run it before getting started on any sound design?

Thanks for your help,

robosax

 

PS -> attached is my PluginList.xml.  tons of doubles! lol  😝 

 

 

This topic was modified 4 months ago 2 times by robosax

   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4292
 

As I said previously, I don't recommend performing repeated full scans. If you insist on doing so, use the "clear list" function on the Operations menu first.

The way the full scan operation works is part of the JUCE platform code. If it has bugs (e.g., introducing multiple entries when only the version number of a plug-in has changed), I prefer not to try to debug it myself.

Note if you update a plug-in, and the vendor's installer simply overwrites the existing file, you don't need to update Unify's Known Plug-Ins list at all. When Unify goes to load the plug-in file, from the same location it has always used, it will end up loading the updated one. The version number may not display correctly in the Known Plug-Ins list, but that's not important. (If you insist on it being up-to-date, delete the list entry manually, then drag/drop the plug-in file into the Known Plug-Ins list.)


   
ReplyQuote
robosax
(@robosax)
Trusted Member
Joined: 3 years ago
Posts: 46
Topic starter  

Posted by: @getdunne

Note if you update a plug-in, and the vendor's installer simply overwrites the existing file, you don't need to update Unify's Known Plug-Ins list at all. When Unify goes to load the plug-in file, from the same location it has always used, it will end up loading the updated one. The version number may not display correctly in the Known Plug-Ins list, but that's not important. (If you insist on it being up-to-date, delete the list entry manually, then drag/drop the plug-in file into the Known Plug-Ins list.)

Thanks for your reply. Shane 😀 

I've installed a few bundles which come with dozens of plugins.  AFAIK, they overwrite existing files.  I scan for updated plugins because I'm also installing new plugins/bundles.  Then Unify keeps showing multiple versions when I right-click and search and also in the Swap: All Instruments(Audio Effects) lists.  It gets confusing with all those doubles.  And in the right-click and search window it doesn't show whether the plugins are mono or stereo, so it lists 4 identical names.

That's why I go through the task of Clearing the list & re-scanning.  Fabfilter, Soundtoys, Kilohearts, PA bundles come with tons of plugins.  Do I have to delete all those old list entries and drag/drop all those plugins to install?  That would definitely take longer than Clearing and re-scanning.

There's gotta be an easier way.  On another note, I recently purchased PluginInfo.app to figure out why I have so many versions.  Maybe I can use that to search through my VST folder and bulk install bundles into Unify.  Installing one or two plugins once in awhile is not that bad.  Some of the bundles are grouped in name, but a lot aren't.  It's those darn bundles! doh!

On a more positive note:  I think update season is over, so I'm good for awhile, but the next one is right around the corner! lol  😆 

Thanks again!

robo

 

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4292
 

@robosax

Thank you for sending the PluginList.xml file, and pointing out where to look for duplicates (e.g. FabFilter). I see now what's happening: When the updated plug-ins are scanned, new entries are created, but the older ones are not getting removed. This used to work; I'm not sure when or why it started misbehaving. I'll look into it.


   
robosax reacted
ReplyQuote
Share: