Differences

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

--- guru-files [2021/09/03 21:06] – [Creating a .guru file] shane
+++ guru-files [2023/05/08 18:59] (current) – external edit 127.0.0.1
@@ Line 72: / Line 72: @@
 The above instructions described how to make a //.guru// file for a single patch library, but //.guru// files can contain multiple libraries, or no libraries (i.e., no top-level //Libraries// folder at all), and anything else that belongs under the main Unify data folder, e.g., you may have a top-level //Presets// folder as in the example, or //MIDI Bank Files//, //MIDI Controller Files//, etc. In such cases, it's strongly advisable to use a working folder.
-Whatever you do, just make sure that the folder structure of your //.guru// file exactly corresponds to where all of your own files need to go. It's a very good idea to test dragging your //.guru// file into Unify, to make sure everything goes into the right places.
+Whatever you do, just make sure that the folder structure of your //.guru// file exactly corresponds to where all of your own files need to go.
+===== Testing your .guru files =====
+It's a very good idea to test dragging your //.guru// file into Unify, to make sure everything goes into the right places. The best way to do this is to create a second "main Unify data folder" somewhere on your disk, and select in Unify using the "Change..." button in the [[settings|Settings view]]. That way, there will be no risk of messing up your actual Unify data folder contents, and you can switch back after you're finished testing.
+To create a second Unify data folder:
+  - Create an empty folder in a suitable location on your disk, then create empty //Libraries// and //Presets// folders inside it.
+    * If you do not create these sub-folders, Unify will not allow you to select the folder as your main Unify data folder.
+  - In Unify, go to the Settings view, click the "Change..." button, and choose your new folder.
+  - IMPORTANT: **Quit Unify** immediately.
+    * This step ensures that your patch database will not be damaged.
+  - Optionally, copy over any other content you may want (patch libraries, presets, etc.) from your real Unify data folder to your testing folder.
+    * Be very careful that to COPY (not MOVE) files/folders to your test data folder
+  - Re-start Unify
+    * Unify will automatically create an empty database file //presets.db// in your test //Libraries// folder.
+    * If you copied over any libraries, click the lightning-bolt icon at the top of the patch browser, to update this newly-created database to include entries for whatever patches you copied.
+  - Optional, but recommended: Quit Unify again, and zip up your entire test folder.
+    * This will allow you to delete and re-create it quickly, for future tests.
+  - Drag/drop your //.guru// file, and verify that Unify responds as you would wish.
+  - Examine the contents of your test data folder carefully, and verify that all files/folders went into the right places.
+If you notice any problems at steps 7/8, you will need to re-build your //.guru// file accordingly. Before trying it again, delete your entire test data folder, and re-create it as it was at step 6, by unzipping the zip file you created at step 6. Then you can simply re-start Unify and repeat steps 7/8.
+When you are finished testing:
+  - Go to Settings, click the "Change..." button, and re-select your original Unify data folder.
+  - **Quit Unify** immediately, then re-start
+    * Everything should now be back exactly as it was, including your patch database.