This article contains hints on troubleshooting missing plug-ins.
Table of Contents |
Checklist for Solving
- Restart your computer after plug-in installation.
- Check locations (correctly installed into your Plug-in folder? Correctly defined Plug-in folder path in DAW?)
- Restart your DAW (most DAWs scan plug-ins only on startup OR if triggered manually).
- macOS: Check if your DAW needs to be running in Rosetta mode as some plugins might not be compatible with Apple Silicon chips.
- Check if your DAW allows you to see all plug-in formats (for example, some plug-ins might be only available as VST2 but not VST3.)
- Make sure you are on a 64-bit system (32-bit is not supported).
- Check whether you're using the correct tracks (some DAWs have limitations for which tracks can host Instruments vs Effects or need to be stereo tracks).
- Virtual Pianist and Usynth plug-ins use a "frame" to group individual titles, so you'll only see "Virtual Pianist" or "USYNTH" in your plug-in list. After adding one of these to a track, click the the title (e.g SCORE) in the upper left to toggle between plug-in controls and the installed titles.
Important question:
-
Did you already define a dedicated Plug-in folder?
- If yes, make sure to add your path while installing the Plug-in (setup step "Select Plugin Locations")
- If no, point your DAW at the standard installation path used while installing (see below for details)
standard installation path for UJAM Plug-ins on Windows
Why you should use a special folder for your Plug-ins
In most DAWs you have the opportunity to define a folder which contains your Plug-ins. This enables you to install all Plug-ins in one location and let multiple DAWs use them independently (e.g. FL Studio, Ableton Live, ProTools ...). As a consequence, no Plug-in manufacturer knows exactly where the Plug-in should be installed into on a specific system, so most of them will just create a standard folder to install the Plug-in to (for UJAM Plug-ins on Windows this is "{SYSDRIVE}\Program Files\VstPlugins\UJAM\"). The result is that you have multiple folders of Plug-in manufacturers with their individual Plug-ins inside, spreaded on your system.
Most DAWs do not check unlimited numbers of folders or locations, so it is a good idea to unify them into one Plug-in folder. Just create a new folder at a location where you don't stumble over it all the time, call it e.g. "DAW Plugins" and install all your Plug-ins inside this folder. If you buy a new DAW and need to set it up, simply define this folder as your Plug-in folder and all installed Plug-ins from all manufacturers should be visible for your Software.
The standard paths can look like this:
Windows 64 bit
| VST | {SYSDRIVE}:\Program Files\VstPlugins\UJAM\ | .dll |
| AAX | {SYSDRIVE}:\Program Files\Common Files\Avid\Audio\Plug-Ins | .aaxplugin |
32-bit plug-ins on 64-bit Windows:
-
{SYSDRIVE}:\Program Files(x86)\VstPlugins\UJAM\
macOS
| VST | {SYSDRIVE}:/Library/Audio/Plug-Ins/VST/UJAM | .vst |
| AU | {SYSDRIVE}:/Library/Audio/Plug-Ins/Components | .component |
| AAX | {SYSDRIVE}:/Library/Application Support/Avid/Audio/Plug-Ins | .aaxplugin |
Unusual: {SYSDRIVE}/User/Name/Library/Audio/Plug-ins/VST/
How to point your DAW to your Plug-in folder
Go to your DAWs settings window (sometimes called "Preferences" or "Options") and look for the "Plug-ins" section. Search for "Plug-in Path" / "Plug-in folder" or sometimes "VST folder" and insert the path you used while installing your Plug-ins. This shows the software where you decided to put your Plug-ins. The DAW scans this folder during startup.
Below a few pictures of standard DAWs and their Plug-in settings:
FL Studio ''Plug-in Manager''
Reaper ''VST plug-ins settings''
Ableton Live ''Preferences''
Verify plugin software is correctly installed
Many Plug-ins consist of two main files:
- the content file (e.g. *PlugInName*.blob)
- the Plug-in (e.g. *PlugInName*.dll for VSTs)
Check whether these files are indeed located at the locations defined during installation.
macOS example:
{SYSDRIVE}:/Library/Application Support/UJAM/FIN-VOOD.blob
The relevant plug-in file will be named after the plugin, in this format: [PluginCategory]–[PluginName]. For example, the plug-in folder for Virtual Guitarist IRON will be named VG-IRON.
If the relevant plug-in files are not in the above folders, uninstall and re-install the plugin (preferably as administrator):
Rescan for Plugins
If the relevant plug-in files are now in the right folders, restart your computer, launch your DAW and check whether the issue persists.
If the issue persists, perform a re-scan in your DAW. Have a look at these articles: How to re-scan Plug-ins in my DAW?
Now you should be ready to make some music! We wish you a lot of creativity and fun with your new ujam plug-ins!
Additional Troubleshooting
- Remember that 32-bit hosts cannot load 64-bit plug-ins while using 32-bit plug-ins in 64-bit hosts require a bridging solution.
- If your plug-in is not working, the installation might be corrupted. Uninstall and reinstall the latest version of the plug-in (preferably as administrator).
- UJAM Finishers, UFX and VOXCRAFT are effects, not virtual instruments. Make sure to add them to the respective Effects or Audio FX section (this can be slightly different and depends on the respective DAW).
- Pro Tools users: Make sure to create stereo tracks for UJAM Virtual Instruments (you won't see them on mono tracks).
- LUNA users: UJAM effects can't be used on mono tracks. Move anything from a mono track to a new stereo track, or add a send to a stereo Bus an add the UJAM effects there.
- Make sure you are using a DAW which supports VST/AU/AAX (not Adobe Audition, Audacity, or Pro Tools First).
- Update your operating system if you're lower than Windows 7 or macOS X 10.11 (our plug-ins are not supported).
- Update your DAW to the newest version. Cubase 5 for example, might not work as expected.
Comments
0 comments
Article is closed for comments.