Loading and playing patches in Unify should be as simple as clicking on the patch name in the patch browser. This page also covers how this might go wrong, and how to recover.

If you open the patch browser (see next section) and don't see any patches, one of three things may be wrong:

1. You haven't installed the Unify Standard Library yet: check these instructions
2. The path to the Unify data folder on the Settings page might be incorrect: check these instructions
3. You need to rebuild the patch database: click the “gear” icon at bottom right to open the Settings page, and click the “Rebuild Now…” button.

If you see some patches, but fewer than you expect, you almost certainly need to rebuild the patch database.

Unify's patch browser view lives in the sidebar extension on the right-hand side of the GUI, which may not always be visible. Click the browse button to open and close it:

The patch browser consists of two main sections:

1. The top section (outlined in red in the picture above) is called the Selector, and contains controls to allow you to narrow down the available choices in the bottom section.
2. The bottom section (also outlined in red) is called the Chooser; it contains a list of patch names in alphabetical order. Click once on any patch name to load that patch.

In addition to these two main sections are three less-obvious things you need to know about:

1. Between the Selector and Chooser is a grey “split bar” which you can drag to adjust the relative heights of the two main sections.
2. To the left of the sidebar itself is another split bar (like the first one, it lights up bright blue when you roll the mouse pointer over it), which you can drag to adjust the width of the sidebar.
3. To the left of the browse button are two buttons with up- and down-pointing green chevrons (see below)
   • Click the downward-pointing chevron button to load the next patch listed in the Chooser
   • Click the upward-pointing chevron button load the previous patch

When you first open the patch browser, the Chooser (bottom part) will show all patches on your system, which may run to many hundreds once you have more than a few libraries installed.

The controls in the Selector (top part of the sidebar) allow you to narrow down the set of patches in the Chooser, to help you find what you want quickly:

The icons at the top-left and top-right are as follows:

• Click the “heart” icon to toggle showing only patches you have marked as “favorites” (by clicking the heart icon next to the patch name in the Chooser section).
• The “lightning bolt” icon icon; click this to rebuild the patch database.
• Click the “X” icon at the right-hand side of the search box (as of v1.1.x) to clear the search box text.

The various scrolling lists in the patch browser (not the pop-up menu of libraries) are multi-selection lists, i.e. you can select (highlight) one or more items, by using various modifier keys while clicking:

• Click (no modifiers) to select an item, and simultaneously de-select all others
• CTRL + Click (CMD + Click on Mac) to toggle an item's selection
• SHIFT + Click to select a range of items (click 1st item, Shift+click last in the range)

• Left-click any patch-name in the chooser to load the patch, replacing any previously loaded patch.
  • Be careful, as this may discard any changes you may have made and not yet saved.
  • Unify does not yet have any “undo” mechanism, nor does it yet warn you that changes may be lost in this way.
• Right-click any patch-name to pop up a menu with additional options as follows:
  • Load patch: This is the same as left-clicking the patch name
  • Add all layers to current patch: Attempts to load the patch's layers as additional layers into the currently-loaded patch. This allows you to create a composite patch from partial layer-groups you have saved as patches previously.
    • Unify will load as many of the patch's layers as possible, but may not be able to load all AUX layers.
    • The patch's MASTER EFFECTS layer will NOT be loaded.
    • Unify will attempt to maintain connections between MIDI, INST, and AUX layers.
  • Add INST1 layer to current patch Loads only the patch's first INST layer as a new layer in the current patch.
  • Load into new Unify layer: Creates a single new INST layer, using an instance of Unify itself as the instrument plug-in, and loads the selected patch into that. See Using Unify itself as an Instrument plug-in in Unify
  • Unify / No Pitch Shift: As above, but modifies certain MIDIBox settings.

As of Unify 1.4, after loading a new Unify layer, if you decide you only need the first INST layer (very common for “unified” patch libraries having only one INST layer per patch), you can click on the layer's operations menu (concentric circles menu at right end of layer) and choose “Replace with embedded INST1”.

After you have loaded one patch by clicking on its name, you can advance to the next one by clicking on the downward-pointing chevron button beside the browse/init/revert/save buttons at the top of the GUI, or simply pressing the cursor-down key on your computer's keyboard. You can go back to the previous patch using the upward-pointing chevron button, or the cursor-up key.

You can toggle the “heart” icon beside any patch name (which indicates if that patch is marked as a favorite) by clicking directly on the icon. You can do this for any patch, not just the currently-loaded one. Once you have loaded a patch, you can quickly toggle its “heart” icon by pressing the F key on your computer keyboard.

All the controls in the Patch Selector make use of Unify's patch database, which is basically an index to all the patches on your system.

• To see the how the database is structured, open the Settings view by clicking on the “gear” icon at the bottom right, and click the “View Database…” button.
• For every patch, the database keeps track of the patch name, the file name (which need not be the same as the patch name), what folder it is in, which library it's part of (which need not be the same as the name of the folder it's in), and lots of other details.
• Whenever you add patches or libraries to your system, Unify needs to rebuild the patch database by re-scanning the patch files. This happens automatically each time you add new content using a .guru file, and you can force a rebuild at any time by clicking the “Rebuild Now…” button in Settings view.

Unify can only work with patch files (types .upf, .unify) in sub-folders of the main Libraries folder (i.e., the Libraries folder inside whatever folder you designated as the main Unify data folder; you can check the path to this in the Settings view).

Because scanning all these files repeatedly would be slow, Unify creates a list or index of them, which we call the “patch database”. The patch browser lists the entries in the database, not the actual files. Any time you create, delete, or move patch files outside of Unify, the patch database will no longer correspond to the files; that's why we have a “rebuild database” button.

When you click the rebuild database button, Unify scans all sub-folders of the main Libraries folder, looking for .upf and .unify files. It opens and reads every single one, to extract the “patch metadata” (patch name, library name, authors, tags, categories, comments, etc.), and puts all this into the database.

As of Unify v1.2.0, Unify can rebuild the patch database in either of two ways: Incremental and Full.

When you click the “lightning bolt” icon, Unify performs an incremental rebuild. It scans all folders under the main Libraries folder, looking for .upf or .unify files, and checks their “last modification” date/time against the database. If the file is newer, Unify will open it and update the database record. If it does not appear to have changed, it will ignore it and skip ahead. It will also add new records for any files which are not yet in the database, and delete records which no longer have an associated file.

This incremental rebuild method, which can be very quick if few or no files have changed, will be all you need in most cases. If you ever suspect that the database may have errors, you can perform a full rebuild by holding down the Option/Alt key while clicking the lightning bolt. Unify will perform the following steps:

1. Create a temporary file favorites.xml in the Libraries folder, listing the names of all patches you had marked as “favorites” (heart icon).
2. Delete the old database file (presets.db).
3. Scan through the .upf and .unify files and create a new presets.db from the patch metadata, as described above.
4. Read the temporary favorites.xml file again, to re-mark the indicated patches as favorites.
5. Update the displayed patch browser.

As mentioned in the section above, each patch file's metadata includes the patch name and the library name. This makes each patch file entirely self-contained, but it can lead to some confusion. You would expect the patch name to match the file name, and the library name to match the name of the containing folder, but this is absolutely NOT required.

Based on these details, here are some specific tips for patch management:

• Avoid manipulating patch files manually (in the Finder/Explorer) as much as possible.
  • Whenever you do manipulate files manually, click the “rebuild database” button in Unify when you are done.
• Never click the “rebuild database” button in one Unify instance, while another instance is still rebuilding.
  • (Normally the buttons will be deactivated, making this impossible, but in a few unusual cases they might not be.)
• If you want to make backup copies of patches you have created, put them anywhere except under the main Libraries folder. This will ensure they won't be found when rebuilding the database.
• If you want to work with a reduced set of libraries for some reason, you can move entire library folders into a new temporary location (e.g., make a folder beside the main Libraries folder, call it something like “Inactive Libraries”, and move some library folders in there) and rebuild the database.
• Manually changing a patch's file name will not change the displayed patch name, even after rebuilding.
  • To change a patch's name, you must re-save the patch, and change the name in the save dialog.
• Manually moving a patch file from one library folder to another will not make it part of the new library.
  • To change a patch's associated library name, you must re-save the patch, and select the new library name in the save dialog.
  • It is strongly recommended (but NOT required) to save the patch into the library folder for the new library. Unify will automatically select the correct folder when saving, but will not stop you from saving the file somewhere else.