Unify Manual

Your complete reference to PlugInGuru's creative playground!

User Tools

Site Tools


troubleshooting

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
Next revisionBoth sides next revision
troubleshooting [2020/01/07 18:52] – [Plug-ins that Unify cannot yet load] shanetroubleshooting [2020/06/29 16:20] – [Issues with bundled plug-ins] shane
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. **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.===== +===== Known issues and limitations in Unify 1.===== 
-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.
  
 ---- ----
  
 ===== Problems installing the Unify Standard Library ===== ===== Problems installing the Unify Standard Library =====
-A few users have reported that, when they try to drag/drop the //Unify Standard Library.guru// file onto Unify, the mouse cursor turns into a circle with a diagonal line through it, and they can't drop the file in. **This will happen if you accidentally select more than one file** before starting the drag operationMake sure **only** the //.guru// file is selected, and drag **just that one file** into the Unify GUI window.+**If you accidentally CANCEL loading the //Unify Factory Content.guru// file during installation:** 
 +If you hit the "Cancel" button instead of "Open" when selecting the //Unify Factory Content.guru// filejust 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 ===== ===== Plug-in scanning issues =====
 Unify's plug-in scanning system is quite robust, but occasionally, it may report that a particular plug-in can't be loaded, even though it actually can. When this happens, locate the plug-in in the Mac Finder or Windows Explorer and drag/drop its icon directly into the Known Plug-Ins view. This will often correct the problem. Unify's plug-in scanning system is quite robust, but occasionally, it may report that a particular plug-in can't be loaded, even though it actually can. When this happens, locate the plug-in in the Mac Finder or Windows Explorer and drag/drop its icon directly into the Known Plug-Ins view. This will often correct the problem.
  
-In a few rare cases, the //PlugScanner// helper app may get stuck on one particular plug-in, re-starting again and again. If this happens:+In a few rare cases, the //PlugScanner// helper app may get stuck on one particular plug-in, re-starting again and again. This should not happen at all in Unify v1.0.6 and later, but IF it does:
   - Cancel the scan   - Cancel the scan
   - Locate the problem plug-in in the Mac Finder or Windows Explorer, and move it to some other folder   - Locate the problem plug-in in the Mac Finder or Windows Explorer, and move it to some other folder
Line 20: Line 32:
   - Try the drag/drop method to re-scan just that plug-in---this works in many cases.   - Try the drag/drop method to re-scan just that plug-in---this works in many cases.
  
 +If you're not sure exactly which is the "problem" plug-in at step 2, you can find out as follows:
 +  * Watch the //PlugScanner// dialog to get a rough idea of which plug-in is the problem one
 +    * It scans in reverse alphabetical order, so you only need to be close
 +  * Moving a **group of plug-in files**---from a little before, to a little after where //PlugScanner// keeps getting stuck---out of the plug-in folder.
 +  * Re-run the scan, to see if it can get past the problem plug-in.
 +  * Once the scan makes it to the end, move the plug-ins back into the original folder, one at a time and re-scanning until you find the one that makes //PlugScanner// crash.
 +  * Carry on from step 2 above
 +
 +If you run into any problems with the plug-in scanner, we'd like to hear about them. Any feedback you can provide COULD be the information we need to understand why something isn't working. So email us at unifysupport@pluginguru.com if you have any information to share.
  
 ===== Plug-ins that Unify cannot yet load ===== ===== 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. Where possible, the plug-in format and operating system are indicated in parentheses.+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 areThe plug-in format and operating system are indicated in parentheses, where known.
  
   * **AIR Music Technology**   * **AIR Music Technology**
Line 28: Line 49:
   * **Lennar Digital**   * **Lennar Digital**
     * Sylenth     * Sylenth
 +  * **Slate Digital**
 +    * All AU plug-ins? (Mac)
   * **Softube**   * **Softube**
     * ALL Softube plug-ins (Mac)     * ALL Softube plug-ins (Mac)
Line 35: Line 58:
     * Superior Drummer, EZKEys or any other Toontrack products     * Superior Drummer, EZKEys or any other Toontrack products
   * **u-he**   * **u-he**
-    * Twangstrom (VST, Windows)+    * Twangström (VST, Windows)
   * **UVI**   * **UVI**
-    * //Falcon// (VST, Windows 10)+    * Falcon (VST, Windows 10)
   * **Waves Audio**   * **Waves Audio**
     * All instrument plug-ins     * All instrument plug-ins
Line 43: Line 66:
  
 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. 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,
  
 ===== Issues with bundled plug-ins ===== ===== 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.+<del>**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.</del> 
 + 
 +This has been fixed. Make sure you are running the latest v2.3.1 version of BlueARP, which is installed automatically with recent versions of Unify.
  
 {{::bluearp-bug-1.png|}} {{::bluearp-bug-1.png|}}
troubleshooting.txt · Last modified: 2023/05/08 18:59 by 127.0.0.1