Notifications
Clear all

Known Plugins is not consistent in DAW vs Stand-Alone Unify

11 Posts
3 Users
1 Likes
614 Views
Daren
(@daren)
Trusted Member
Joined: 3 years ago
Posts: 59
Topic starter  

Hi Shane, 

I'm encountering some sort of bug.  I've loaded/scanned for new plugins in Unify Stand-Alone and those plugins work fine.  However, when I open Unify within the DAW, I get the error message and everything is red. Those plugins do not show up on the "Known Plugins" list.   I would have to scan those plugins again (Unify within DAW) for it to show up on the "Known Plugins" List.  Usually, it's just works with scanning once in the Stand-Alone.

Thanks in advance!

DAW is GB & Logic Pro.


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

@daren

This is very unexpected. Which version of MacOS are you running? This might be some new quirk I was not aware of.


   
ReplyQuote
Daren
(@daren)
Trusted Member
Joined: 3 years ago
Posts: 59
Topic starter  

Hi Shane,

I'm on (Intel chip) MacOS Catalina 10.15.7.  It's really odd as if I'm working with "two" separate Unify database of plugins. 
Thanks.

[img] [/img]

[img] [/img]


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

@daren

Unify's plug-in database is stored on a per-user basis at ~/Library/Application Support/PlugInGuru/PluginList.xml. Is it possible you might be running the Unify stand-alone and your DAW under different login accounts?

Also: could you please post the corresponding screenshots showing Unify's Known Plug-Ins view, instead of the pop-up menus?


   
ReplyQuote
Daren
(@daren)
Trusted Member
Joined: 3 years ago
Posts: 59
Topic starter  

@getdunne 

I'm the only using my computer and the same login account. 

Note:  I also upgraded my external SSD, copied my entire sample libraries over and pointed Unify to the correct drive and double check stand-alone and within DAW, plus rebuilt the database.

I've done the basics troubleshooting such as cold-reboot, etc but still perplexed.  

Sure. Here's both views of the Known-Plugins (both Stand-Alone and in-Daw show Unify v1.6.2):

[img] [/img]

[img] [/img]


   
ReplyQuote
Daren
(@daren)
Trusted Member
Joined: 3 years ago
Posts: 59
Topic starter  

Here's a screen capture of my  ~/Library/Application Support/PlugInGuru/PluginList.xml
It's showing all of my Spitfire Originals which reflects correctly with what I'm seeing in the stand-alone "known plugins."

[img] [/img]


   
ReplyQuote
pluginguru
(@pluginguruforums)
Honorable Member Admin
Joined: 5 years ago
Posts: 321
 

Hi Daren - this is John Lehmkuhl and I'm checking the Known PlugIns list on my Mac between standalone and Unify in Logic Pro X (note I'm only able to use up to version 10.4.4 due to how old my Mac Tower is). The lists are in sync and identical so this is very odd. I don't think we've heard of this issue before in almost 2 years so congratulations on bringing up a real mystery.

 

Apples Spotlight sucks big time when it comes to searching for filenames on your computer. If you don't have a better search utility, I'd suggest getting Find And File (FAF) or use whatever you might have and search to see how many files are on your computer HD with the name "PluginList.xml". I found only one and I'm curious how many will show up on your HD. Please let us know so we can track down this discrepancy.

 

Thank you!

- John Lehmkuhl

Life is Sound / Sound is Divine
www.pluginguru.com


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

@daren

@pluginguruforums' (John's) suggestion to search for extra PluginList.xml files is a good one. You'll probably find one somewhere under the main Unify data folder--that's the OLD one; it should be deleted. The new/current one lives in ~/Library/Application Support/PlugInGuru; leave that one alone.


   
ReplyQuote
Daren
(@daren)
Trusted Member
Joined: 3 years ago
Posts: 59
Topic starter  

@pluginguruforums @getdunne

Hi John & Shane!

Thanks for suggesting this!  Mystery solved.  I found two files. Here are my findings (also see attached image):

If I switch to between GarageBand and Logic for projects (depending on what colleagues use on their end), GB has its own container folder with its own PluginList.xml file.   I double checked the path with Logic and also Cubase and it uses the correct PluginList.xml file as pointed out by Shane. 

I've deleted the pluginList.xml file in the GB folder so Unify doesn't work properly.  Is this one of Apple's design quirks? Shouldn't all DAWs use the same path for the PluginList.xml file? 

Thank You! 


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

@daren

Thank you for finding this! Yes, it seems to be a MacOS quirk, probably something quite recent. I will have to do some research to see if there's a way around this. Otherwise, it may be necessary to get clever with symbolic links.


   
Daren reacted
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@daren

I've looked into this a little further. The issue is that GarageBand is a "sandboxed app", so MacOS does all these tricks to isolate it AND the plug-ins it loads from the file system. I now realize (too late!) that I made a poor choice for where Unify's settings and known plug-ins list files should reside.

I had tested Unify in GarageBand, but not a lot, and it was quite a while ago. I can't believe I missed something so fundamental. I can only imagine that almost no other users have tried using Unify in GarageBand.

This is likely to take a long time to figure out. If you would like to help out with this over the next few months, please email UnifySupport@PlugInGuru.com, mention this topic, and ask to be added to the beta-tester list.


   
ReplyQuote
Share: