Unify Manual

Your complete reference to PlugInGuru's creative playground!

User Tools

Site Tools


playing-patches

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
playing-patches [2022/02/17 23:54] – [Patch count and load-options menu] shaneplaying-patches [2023/05/13 13:58] (current) – [Incremental vs Full rebuild] shane
Line 72: Line 72:
 ===== Using the Patch Chooser ===== ===== Using the Patch Chooser =====
   * **Left-click** any patch-name in the chooser to **load the patch, replacing any previously loaded patch**.   * **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:   * **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     * **Load patch:** This is the same as left-clicking the patch name
Line 82: Line 80:
     * **Add INST1 layer to current patch** Loads only the patch's first INST layer as a new layer in the current patch.     * **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 [[embedded-unify|Using Unify itself as an Instrument plug-in in Unify]]     * **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 [[embedded-unify|Using Unify itself as an Instrument plug-in in Unify]]
-    * **Unify / No Pitch Shift:** As above, but modifies certain [[midibox|MIDIBox]] settings. +    * **Unify/drum (No Pitch Shift):** As above, but modifies certain [[midibox|MIDIBox]] settings. 
 +    * **Copy patch name to clipboard**: Does what it says, without having to load the patch. 
 +    * **Reveal in Windows Explorer** (**Reveal in Finder** on Mac): allows you to locate the patch file.
 **As of Unify v1.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". **As of Unify v1.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".
  
Line 94: Line 93:
 ==== Patch count and load-options menu ==== ==== Patch count and load-options menu ====
  
-**As of Unify v1.7**, a small "footer" may appear at the bottom of the Chooser area (depending on your settings; see [[settings|Using the Settings view]]):+**As of Unify v1.7**, a small "footer" may appear at the bottom of the Chooser area (depending on your settings; see [[settings|Using the Settings view]]). This was revised somewhat in Unify v1.8, as shown:
  
 {{::browser-4.png|}} {{::browser-4.png|}}
Line 118: Line 117:
 **Note** random shared patch files might not load perfectly on your system, as they may require additional files such as samples. Unify's [[guru-files|.guru files]] mechanism is a better method for sharing groups of related files or entire libraries. Unify will try to load the patch as best it can, and if you choose to save it, you may need to update some aspects, such as the library name, to match the library folders on your system. **Note** random shared patch files might not load perfectly on your system, as they may require additional files such as samples. Unify's [[guru-files|.guru files]] mechanism is a better method for sharing groups of related files or entire libraries. Unify will try to load the patch as best it can, and if you choose to save it, you may need to update some aspects, such as the library name, to match the library folders on your system.
  
 +You can then make any changes you like and save it to (typically) your User Library.
  
- 
- 
-You can then make any changes you like and save it to (typically) your User Library. 
 ===== OOPS, I clicked a patch and lost all my work! ===== ===== OOPS, I clicked a patch and lost all my work! =====
 In versions of Unify before v1.5, it was all too easy to lose work by clicking on a patch in the Chooser. In versions of Unify before v1.5, it was all too easy to lose work by clicking on a patch in the Chooser.
Line 199: Line 196:
  
 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. 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.
 +
 +**As of Unify 1.10.x**, incremental rebuild has been further optimized as follows:
 +  * If all libraries are selected, and no library-subset is active, works as described above.
 +  * If a library-subset is active, and no specific one is selected, only the libraries in the subset are scanned.
 +  * If a library is selected, only the selected library folder is scanned.
  
 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: 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:
playing-patches.1645142070.txt.gz · Last modified: 2023/05/08 18:59 (external edit)