Unify Manual

Your complete reference to PlugInGuru's creative playground!

User Tools

Site Tools


scanning

Differences

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

Link to this comparison view

Next revision
Previous revision
scanning [2019/11/29 01:08] – created shanescanning [2023/05/08 18:59] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Scanning and using your own plug-ins ====== ====== Scanning and using your own plug-ins ======
-When scanning for plug-ins, Unify actually has to try to load each one, and this process can be error-prone, even causing the program to crash occasionally. We therefore recommend the following "pro tips".+Before you can use any of your own plug-ins with Unify, they must be registered in Unify's [[plugins#unify_s_plug-in_database|plug-in database]]. You can register plug-ins individually, or you can have Unify scan your system for available plug-ins. 
 + 
 +===== Registering individual plug-ins ===== 
 +**You don't have to run a full scan for plug-ins.** 
 + 
 +You can **register plug-ins individually** in one of two ways: 
 +  - Locate the plug-in file and drag/drop its icon into Unify's //plug-ins view// 
 +  - Click the "Operations..." button at the bottom-left, and choose "Select plug-in(s) to scan" 
 +    * A standard open-file dialog will appear 
 +    * Locate and select the plug-in you want to register, and click "Open" 
 + 
 +===== Scanning your system for plug-ins ===== 
 +You can also have Unify scan your system for available plug-ins. Note that when when scanning for plug-ins, Unify actually has to try to load each one. This will certainly trigger any copy-protection mechanisms it uses, and in some casesmay even cause Unify to crash. We therefore recommend the following "pro tips".
  
 ==== Pro tips for scanning ==== ==== Pro tips for scanning ====
Line 24: Line 36:
 VST/VST3 plug-ins are often stored in //nested// structures of folders, e.g., on a Windows system, you might have most plug-ins in, say, //C:\Program Files\Common Files\VST2//, which also contains a sub-folder called //Plogue Art et Technologie, Inc//, containing all of that company's plug-ins. If you select the top-level folder, Unify will scan into the sub-folder(s) as well, but you could also specify just the path to the sub-folder instead, and Unify would not attempt to scan all the others. VST/VST3 plug-ins are often stored in //nested// structures of folders, e.g., on a Windows system, you might have most plug-ins in, say, //C:\Program Files\Common Files\VST2//, which also contains a sub-folder called //Plogue Art et Technologie, Inc//, containing all of that company's plug-ins. If you select the top-level folder, Unify will scan into the sub-folder(s) as well, but you could also specify just the path to the sub-folder instead, and Unify would not attempt to scan all the others.
  
-Once you have edited the folder list the way you want, click the "Scan" button to begin the scan. The dialog above will be replaced by another one showing the progress of the scan.+Once you have edited the folder list the way you want, click the "Scan" button to begin the scan. The dialog above will be replaced by another one showing the progress of the scan:
  
-**Unify may CRASH during scanning.** This is actually normal (we're working on improving this), and all you need do is start Unify again, and re-start the scan, and it will continue from where it left off. This is the main reason why it's best to use the stand-alone Unify app, because if the Unify plug-in crashes, it will take your DAW down with itand there will be more steps involved in re-starting.+{{::plugin-4.png|}} 
 + 
 +This new dialog is actually a separate "helper" program called //PlugScanner//. You can drag the //PlugScanner// dialog to a different location on your screen, and continue using Unify normally even while it's running. The "CANCEL" button in the //PlugScanner// dialog allows you to stop the scan gracefully, e.g. if you decide you'd prefer to do the scan another time. 
 + 
 +Back in the Known Plug-Ins view in Unify, a progress message in green text will appear at the bottom of the main window, and the "Operations" button will change to "CANCEL SCAN" in red. Unlike the CANCEL button in the //PlugScanner// window, this one actually shuts down //PlugScanner// forcefully. Use it only if you think //PlugScanner// is completely stuck, but give it a bit of time--some plug-ins take surprisingly long to test, so you might see no apparent activity for a minute or more at times. 
 + 
 +**PlugScanner may CRASH during scanning.** Unify will automatically re-start it, and it should continue from where it left off. If you moved the //PlugScanner// window, you'll immediately know that it was re-started, because it will seem to jump back to where it was at first. 
 + 
 +In a few rare cases, **PlugScanner may get stuck on one particular plug-in**, re-starting again and again. If this happens: 
 +  - Cancel the scan 
 +  - Locate the problem plug-in in the Mac Finder or Windows Explorerand move it to some other folder 
 +  - Start the scan again 
 +  - Once you are able to scan all the way to the endyou can move the problem plug-in back where it was. 
 +  - Try the drag/drop method to re-scan just that plug-in---this works in many cases.
  
 **Various pop-up windows may appear during scanning.** This is why we advise staying near your computer, so you can click "OK" or whatever, to allow the scan to continue. **Various pop-up windows may appear during scanning.** This is why we advise staying near your computer, so you can click "OK" or whatever, to allow the scan to continue.
Line 35: Line 60:
 Once a scan eventually completes, **you may see one or more items in red text** at the bottom of the plug-in list, with an indication that they "appeared to be plug-ins" but couldn't be opened properly. Once a scan eventually completes, **you may see one or more items in red text** at the bottom of the plug-in list, with an indication that they "appeared to be plug-ins" but couldn't be opened properly.
   * In some cases, these are not plug-ins at all, but simply auxiliary files stored in the same folders. These can safely be ignored.   * In some cases, these are not plug-ins at all, but simply auxiliary files stored in the same folders. These can safely be ignored.
-  * Occasionally, you might see a file listed which you're pretty sure is a plug-in. **Try the drag/drop method to re-scan just that file**--this works in many cases. +  * Occasionally, you might see a file listed which you're pretty sure is a plug-in. **Try the individual registration method (see top of this page) to re-scan just that file**---this works in many cases.
- +
-We are well aware that Unify's plug-in scanning is far from perfect, and we hope to release an improved version in a future update. In the meantime, we appreciate your patience!+
  
scanning.1574989724.txt.gz · Last modified: 2023/05/08 18:59 (external edit)