Differences

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

--- troubleshooting [2020/03/06 02:40] – [Problems installing the Unify Standard Library] shane
+++ troubleshooting [2023/05/08 18:59] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 **This page is UNDER CONSTRUCTION** and will change as users report specific issues. If an issue you're facing isn't listed here, let us know (<UnifySupport@PlugInGuru.com>) and we'll add it.
-===== Known issues and limitations in Unify 1.0 =====
+===== Known issues and limitations in Unify 1.x =====
-As with any "version 1.0" product, Unify still has a few limitations that we'll be working hard to fix through the coming weeks and months.
+As with any "version 1" product, Unify still has a few limitations that we'll be working hard to fix through the coming weeks and months.
 ----
@@ Line 11: / Line 11: @@
 If you hit the "Cancel" button instead of "Open" when selecting the //Unify Factory Content.guru// file, just click the "gear" icon to go to Unify's Settings view, and **click the "Select .guru file..." button**. It's right in the middle---the only colored button on the page.
+===== Duplicate entries in patch browser =====
+A handful of users (all on Windows?) have reported seeing duplicate and even triplicate entries in Unify's patch browser. We don't yet know the cause, but there is a work-around, as follows:
+  - Close Unify if it's open.
+  - Open the main Unify data folder, and go inside the Libraries sub-folder.
+    * If you see a file called //favorites.xml//, RENAME it (e.g. //OLD favorites.xml// or something).
+    * Locate the file //presets.db// (this is the patch database) and drag it to the Trash.
+  - Run Unify again.
+  - Rebuild the patch database.
+Rebuilding the patch database in this way will cause Unify to forget which patches you may have marked as favorites. The renamed //favorites.xml// file MAY be useful to re-mark them. Open it in a text editor and you MAY see a list of the patches you had marked as favorites before. (We say "MAY" because whatever underlying issue is causing the multiple patch entries could also affect the favorites file, so we can't be sure.)
 ===== Plug-in scanning issues =====
@@ Line 34: / Line 44: @@
 ===== Plug-ins that Unify cannot yet load =====
 We are working hard to track down why Unify can't load certain plug-ins. The following is a list of plug-ins which **at least some users** have reported being unable to load - many others are. The plug-in format and operating system are indicated in parentheses, where known.
+**Note this list is out-of-date (as of February 2022).** Since this list was first compiled, Unify has improved, and several vendors have released newer versions of their plug-ins which work better in Unify.
   * **AIR Music Technology**
@@ Line 57: / Line 69: @@
 Please use the [[https://forums.pluginguru.com|PlugInGuru Forums]] to let us know about any more you may discover. We have set up separate forums for plug-in issues on Windows and Mac computers, because it often happens that a plug-in may work on one, but not the other.
-**ALSO** - another alternative way to load Plug-Ins is to drag the plug-ins from your finder into Unify's "Known Plugins" window (click the PlugIn icon bottom Right cluster). This bypasses the scanner and will allow you to load as many files as you select in your finder and drag into Unify,
+**ALSO** - The recommended way to register plug-ins is to drag the plug-in file(s) from Windows Explorer (or Mac Finder) into Unify's "Known Plug-Ins" view (click the "plug" icon bottom Right cluster). This bypasses the scanner, and may succeed in some cases where the scanner fails. If you are unable to drag/drop (some Windows set-ups block it), click the "Operations..." button at the bottom of the Known Plug-Ins view, choose "Select plug-in file(s) to load..." from the menu, and then locate the plug-in files by navigating in the usual way in the file-open dialog which appears.
-===== Issues with bundled plug-ins =====
-**BlueARP: Clicking on pattern-name causes crashing** on Windows systems only. Does not happen on Macintosh. This appears to be an issue in BlueARP itself, and we will work with the author to try to resolve it.
-{{::bluearp-bug-1.png|}}