Unify v1.5 added two safety features, to help with the common mistake of clicking on a new patch before saving the current one:

1. Auto-save ensures that Unify automatically saves the current patch, allowing you to get it back using the Revert button.
2. Are you sure? provides the conventional “are you sure?” warning pop-up whenever you choose an action (loading a patch, hitting Init, or quitting Unify) which would cause you to lose work.

Both of these features are optional. Auto-save is ON by default, are you sure? is OFF by default.

Unify maintains a special folder (Auto-Saved Patches under the main Unify data folder) where it automatically saves a copy of your current patch, any time you might lose it by e.g. hitting the Init button, clicking on a patch in the patch browser to load it, clicking the Next/Prev arrow buttons, or quitting the Unify stand-alone app.

If you do any of these things, and need to get back to the patch you were working on, click the Revert button at the top-right corner of the Unify GUI, to bring up the Revert menu, which will look something like this:

The top menu item is for the original “revert” function–ignore it. The auto-saved patches are listed below this, in reverse time order (most recent first), so you will almost certainly want to click the first one under the horizontal line, indicated by the purple outline in the image above.

If this does not seem to be the patch you wanted, try the next one. If you get flustered, you might accidentally load a new patch, then perhaps even another one. This is why Unify saves more than one.

The auto-save feature is ON by default with Unify set to maintain up to 5 auto-saved patches. See Using the Settings view for details (look for the “On Patch Load” line in the Settings view). You may disable it entirely by choosing “Don't auto-save” from the menu in Settings, but this is not recommended.

The first line on the Revert menu is for the original “Revert” function from earlier versions of Unify. This is used to DISCARD all changes you have made to an already-saved (NOT auto-saved) patch, and simply re-load that patch from disk, just as if you had clicked on it in the browser.

If auto-save is disabled, you will not see the pop-up menu at all when you click the Revert button; the original “revert” function will be triggered, as in earlier versions of Unify.

If you want to have an extra layer of protection against losing work, check the Ask “are you sure?” box in the Settings view. This will ensure that a conventional “are you sure?” warning will pop up anytime you might lose work.

Click OK to complete the action you started (the current patch will still be auto-saved, if auto-save is enabled). Click Cancel to cancel the action and remain where you are (the current patch will not be auto-saved).

Perhaps surprisingly, for a host program like Unify to detect whether or not the current patch has changed is actually quite complicated, because it has no way of knowing what changes may have occurred inside third-party plug-in instances.

Unify uses a simple method to check for patch changes:

• When the patch is loaded, Unify computes and stores a checksum of the patch data.
• When you initiate any action that might overwrite the current patch (Init, patch load, etc.), Unify re-computes the checksum, compares it against the stored one, and will assume the patch has changed if they are not the same.

This checksum algorithm is simple, quick, and unlikely to produce “false negative” results. However, it's also hyper-sensitive–the slightest change can trigger it, even using your mod-wheel, or any MIDI CC control linked to parameters via a macro knob, OR via “MIDI-learn” or programmed linkage within some third-party plug-in.

Unfortunately, there are also some plug-ins which will trigger the checksum algorithm every time, even if nothing has changed in the patch, because they simply work that way. Even the built-in ComboBox utility plug-in does this.

Because of this hyper-sensitivity, you will see the “are you sure?” pop-up a lot, even when you really don't expect to. For this reason, we decided to make it optional, and OFF by default.