Notifications
Clear all

Favorite Plug-in Subsets Not Saving Correctly

8 Posts
2 Users
1 Reactions
973 Views
(@stevek109)
Eminent Member
Joined: 4 years ago
Posts: 25
Topic starter  

I created a subset folder under Audio Effects By Company-->Kilohearts to place all Kilohearts VST effects into. mda Delay, mda Limiter, and mda Stereo effects keep replacing Kilohears Delay, Limiter, and Stereo effects. Several times deleted the subset folder Audio Effects By Company-->Kilohearts and placed all Kilohearts VST effects inside but Delay, Limiter, and Stereo effects are replaced my mda versions. What's going on? Seems if company's VSTs have a generic name like Delay, Limiter, and Stereo they are replaced by the built-in VSTs. Every Audio Effects menu that contains just the word Delay, Limiter, and Stereo is replaced by the mda audio effect version!


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

Hmmm, this shouldn't be happening, because the MDA effects all have names that start with "mda". BUT it evidently is a problem for you, so let's look into it.

Please post a list of the exact names of the Kilohearts plug-ins, as they appear in the Known Plugins list in Unify, and I'll see if I can identify a pattern and figure out what's going on.


   
ReplyQuote
(@stevek109)
Eminent Member
Joined: 4 years ago
Posts: 25
Topic starter  

@getdunne

I dump the entire VST and VST3 database from Unify. After a few hours of scanning my VST and VST3 library, 700+ plugins, the subset folder under Audio Effects By Company-->Kilohearts works correctly again. Now, the Kilohearts delay, limiter, and stereo effects links are working propertly instead of being replaced by the mda delay, mda limiter, and mda stereo. Maybe the Unify VST xml database links get corrupted even though I'm doing a scan of VSTs and VST3 every time I add new VSTs or update VSTs? Does the xml files get corrupted when Unify crashes? I just thought this could be important if other users encounter the same issue. Anyways, thanks for your help.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

I'm glad it's working for you again. I agree this could be important. If anything like this happens again, please let us know and maybe we can track down why.

 


   
ReplyQuote
(@stevek109)
Eminent Member
Joined: 4 years ago
Posts: 25
Topic starter  

@getdunne

I don't know if this is relevant. The BBC Discover patches shared during yesterday's video podcast don't work. I've been using BBC Discover since the first day it was released. I can make my own BBC Discover patches in Unify. I own a number of Spitfire Audio plugins. When trying a BBC Discover patch Unify says there's no such link (to the BBC Discover VST) and fails to load BBC Discover plug-in. This isn't important since the patches were free but I hope future BBC Discover patch libraries will work. I tried the BBC Discover patches again after rebuilding the VST databases, deleting and reinstalling patches, and refreshing the patch database with no luck.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

Two of the BBC Discover patches (the ones with embedded Unify instances) won't work in Unify v1.0.12 as they were originally shared. We have updated versions available (as a .guru file -- drag/drop into the Unify GUI) at https://www.dropbox.com/s/syizu10rh8xp24e/BBC%20DiscoverStation.guru?dl=0 .

If Unify is failing to load the BBC Discover plug-in, it's because it doesn't know where to find it. Is it listed on the Known Plug-Ins view? If not, use the Operations menu "Select plug-in file(s) to scan..." item, locate the VST plug-in, and choose Open, then try those patches again. If you had previously scanned e.g. the VST3 version, that wouldn't work because the data format is not the same.

 


   
ReplyQuote
(@stevek109)
Eminent Member
Joined: 4 years ago
Posts: 25
Topic starter  

@getdunne

That what I thought. Because I was using 1.0.12 and that the patches were created with 1.1 of Unify. Thanks for the clarification.

 


   
bkollee reacted
ReplyQuote
(@stevek109)
Eminent Member
Joined: 4 years ago
Posts: 25
Topic starter  

@getdunne

Same issue with Plug-in Subsets in Unify 1.0.12. Effect plugins with generic names such as Delay, Limiter, and Stereo effects are replaced my mda counterparts. Re-scanning VST and VST3 plug-ins didn't work. The Kilohearts Delay, Limiter, and Stereo effects are replaced my mda equivalents. The Kilohearts plug-ins are named Delay, Limiter, and Stereo, the same generic name as mda versions within Unify's plug-in list. So, it seems I will not be able to make my own categories or sub-lists if the plug-in developer hasn't named their plug-ins other than a generic name! Hopefully, the new version fixes this issue and patch storage issues.


   
ReplyQuote
Share: