Notifications
Clear all

Patch list doesn't update in the sidebar for user libraries

8 Posts
3 Users
1 Reactions
556 Views
RichSilk
(@richsilk)
Active Member
Joined: 4 years ago
Posts: 13
Topic starter  

I have been having problems using the patch browser with user libraries.

I'm using the latest version (1.1.3) on Windows 10 and have rebuilt the patch database multiple times.

With "Unify Standard Library" selected, everything works... I see all the standard patches in the sidebar.

But when I select a user library (which I happened to name "Richard's Library") from the drop-down menu, the patch list does NOT update in the sidebar.

The sidebar does not update when I select "All Libraries" either. The search feature doesn't seem to work either; if I type a search term I know is in the library, no patches show up in the sidebar.

I did some experiments and discovered that if I simply name the library "User Library" instead of "Richard's Library" everything works.. When I select "User Library" from the drop-down the patch list updates as expected.

The only conclusion that I can draw is there is something wrong with the NAME of the library? Perhaps the apostrophe "'" in the library name is causing a problem?

I'm a new user of Unify, so maybe there is something else I'm not understanding about library management, but this appears to be a bug.


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

The apostrophe is the problem, because it's being treated as a "single quote".

I will look into whether or not we can support library names with embedded apostrophes in future. Thank you for reporting this issue.

 


   
ReplyQuote
RichSilk
(@richsilk)
Active Member
Joined: 4 years ago
Posts: 13
Topic starter  

Thanks for the quick reply.

I have about a dozen patches I added to "Richard's Library". I tried moving the .unify files into the "User Library" directory, but the bad library name is baked into the patch. Is there any way to edit the patches to change the library name or do I have to re-create them?


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

Moving files in the Finder/Explorer is not the way to do this, BUT you don't have to re-create your patches. You can simply re-save them under a different library name. However, first you have to be able to get at them, to open them, which is where we started.

I suggest the following:

  1. Locate the folder under .../Unify/Libraries which contains your .unify files, and rename it to something without apostrophes, e.g. "Richard".
  2. In Unify, click the lightning-bolt icon at the top-right of the patch browser, to rebuild the patch database. If your patches are visible, great; you can load each one and click SAVE, selecting a new library from the drop-down menu, then click SAVE AS.

If your patches are still not visible after changing the containing folder name and rebuilding the patch database (I think this is likely), zip them up and post them here, and I'll try to repair them for you.

All these problems arise because we encode the patch name and library name inside each .unify file, to allow the patch name to differ from the file name, and the library name to differ from that of the folder that contains it. It seemed like a great design idea at the start, but has led to no end of trouble. We expect to move to a simpler system in a near-future update, which will allow you to simply move files around as you tried to do, and have it work as you would expect. We're just not there yet.


   
Mark R reacted
ReplyQuote
RichSilk
(@richsilk)
Active Member
Joined: 4 years ago
Posts: 13
Topic starter  

I renamed the directory name to "Richard" and rebuilt the patch database, but unfortunately the name still showed up as "Richard's Library" in the patch browser.

 

I've enclosed a .zip file of the library. If you can repair them, great; otherwise it's not much of a big deal to start over.

Thanks for your help.


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

I fixed the patches; attached.


   
ReplyQuote
Mark R
(@mark-r)
Member
Joined: 4 years ago
Posts: 30
 
Posted by: @getdunne

All these problems arise because we encode the patch name and library name inside each .unify file, to allow the patch name to differ from the file name, and the library name to differ from that of the folder that contains it. It seemed like a great design idea at the start, but has led to no end of trouble. We expect to move to a simpler system in a near-future update, which will allow you to simply move files around as you tried to do, and have it work as you would expect. We're just not there yet.

Wonderful news! "Expected behavior" (instead of complexity) when moving patches around.

@getdunne Thank you!

Studio system: M2 Mac Mini, 16GB, Ventura
old system: 5kiMac from 2014, quad i7, Big Sur 11.6.4


   
ReplyQuote
RichSilk
(@richsilk)
Active Member
Joined: 4 years ago
Posts: 13
Topic starter  

Thanks Shane. The patches are working with the renamed library now.

My issues have been resolved.

Until this behavior is fixed, let this serve as a warning to other users to not use an apostrophe in the name of a library, or you might lose access to your patches.


   
ReplyQuote
Share: