When making libraries for Unify, you have to be very careful about commercial plug-ins:
You also have to think about cross-platform (Mac/PC) issues:
There are a few VERY important details to understand before you start making a patch library for Unify:
While on the subject of library names, don't choose something too generic like “Dance vol.1”. Think ahead to when a user has 80 different libraries. They'll need to be able to find yours easily, so name your library's the way you'd name a band, in a way which is somehow unique to you.
Here’s what you need to do when creating a new library:
If you choose the “New Library…” item in the library list, but Unify does not present a text editor where you can type the new name, it’s because you previously saved some patches without specifying a library at all. This confuses the program.
Once there are NO more patches with a blank Library field, the <none specified> item should disappear from the Libraries menu. If not:
All of your own samples should go into a Samples folder under Libraries/<your library name>. This folder won’t be created automatically; you have to make it yourself. If the parent folder (shown below as “Your Library Name”) doesn’t exist, go back to the top and save one patch there like I said. This will create the parent folder and the Patches folder. COPY (don’t move) all of your samples into the Samples folder, grouped into sub-folders according to the following folder structure:
Note you should not put SFZ files directly inside the Samples folder. They should always be grouped under sub-folders (even if there’s only one), or Guru Sampler won’t be able to load them properly.
The reason you should to COPY, not MOVE your samples is that in all your patches, the saved state every Guru Sampler instance is set to look for them in the user Samples folder beside the Libraries folder. To fix this:
Only AFTER you have fixed every single sample path in this way, you can finally remove the original samples from the user Samples folder (if you want to; it’s harmless to leave them in there).
If you have already created a ton of patches:
These steps should be sufficient to rebuild your library so it’s self-contained. If you can, test on another machine by copying ONLY your library’s main folder. (Make sure to rebuild the patch database on the test machine after you do this.)
At some point in the future, we’ll be adding features to Unify to make some of these procedures a bit more automatic, but that won’t happen soon.