Notifications
Clear all

Unify Libraries on 2 Macs

2 Posts
2 Users
0 Likes
70 Views
(@robert-hunter)
New Member
Joined: 10 months ago
Posts: 1
Topic starter  
Unify on stationary quad i7 iMac and also on a Macbook Pro for shlepping around.
Unify patches being created on both, so I want to be able to share patches I make between both computers as accurately and efficiently as possible. (The same PlugInGuru and 3rd party sound libraries will be on both Macs).
 
Shane Dunne responded with "The quickest way to save whole collections of patches on two or more computers would be to set them all to use a common Unify data folder on a network-shared drive. This would not be ideal, though, because sample files (which are quite large) would load much more slowly over a network connection. The ideal might be to create a new library folder on computer #1, then move it to a network share and replace it with a symbolic link. You could then create similar symlinks in the Libraries folders of computer #2, #3, etc. so while the patches would load (quickly) across the network, any samples they reference would load (very quickly) from each computer's own local disk drive.
If you drop .unify patches one by one into the Unify GUI, Unify will load the patch, but won't save it. If you click Save and then leave the patch and library names unchanged, you will have an opportunity to save it under the original name, and if there is already a patch file matching that name (in the same-named library folder), you will be asked if you want to overwrite it.
One final thought: For your specific situation, the ideal compromise might be to put the whole Unify data folder onto a good, fast external SSD (e.g. Samsung T7), and just plug it into whichever Mac you're using. This will yield the best balance of speed and convenience."

What do you think about using fast SSD-1 as the working drive, and then copying/updating SSD-1 contents to SSD-2 ...(enabling me to use an SSD drive for each Mac when both are running). This also provides a constantly updated backup?? Good idea/bad idea? What problems do I create doing this? Am I actually backing up all library and patches or just big sound files? Maybe I'm sort of back to something like my original question. If I re-ask but say it a bit different ... I think I want to take the time to set up the two macs so that they have identical installs, file management structure, sound file organization, and patches ...which means I'll have to work to keep this all together. Is there a "best practices" or "how to do it" video for this? Based on what Unify has already turned into ...taking the time to get this rock solid before I get any farther along (in the size and amount of files) seems worth it.
 
Shane Dunne responded with "This question has never come up before; hence there is no "best practice" and no videos.

A drive- or folder-mirroring solution such as you suggest will probably work fine. The only potential issue is that, unless the file paths on the "source" and "target" Macs are truly identical, you will probably need to fully rebuild the patch database on the target machine each time. Unfortunately, several users have reported that this operation results in loss of their designated favorite patches. I still don't know why this happens; it may be related to folder permissions.
If you bring this question to our Forum (create a new topic in the "Questions about Unify" section), I will work back and forth with you to get this working. If necessary, you can zip and post files (e.g. the patch database file Presets.db, found in Unify's Libraries folder) which I can analyze to track down problems."
 
THANKS for replies and any future effort on these topics Shane. 

   
Quote
Topic Tags
Robert.P
(@robert-p)
Reputable Member
Joined: 4 years ago
Posts: 290
 

Posted by: @robert-hunter

A drive- or folder-mirroring solution such as you suggest will probably work fine. The only potential issue is that, unless the file paths on the "source" and "target" Macs are truly identical, you will probably need to fully rebuild the patch database on the target machine each time.

This would be probably the best solution - two external SSDs (one for each Mac) with identical folder structure + application instantly synchronizing files over the local network 

 


   
ReplyQuote
Share: