Default File Locations for UJAM products

Introduction: Why File Locations Matter

Understanding where UJAM products store their files is essential for troubleshooting, managing disk space, and ensuring a stable music production environment. This guide provides a comprehensive reference for all default file locations on both macOS and Windows operating systems.

A complete UJAM plugin installation consists of three distinct types of files :

• The Plugin File: This is the core application that loads into a Digital Audio Workstation (DAW). It has an extension like , .dll, .vst3, .component, or .aaxplugin and contains the user interface and audio processing engine.
• The Content Library (.blob file): This large file, often several gigabytes in size, contains all the audio samples, instrument recordings, and sound assets for the plugin. It is designated with a .blob extension, which stands for "Binary Large Object".
• User & Authorization Data (.ops file): This category includes small, user-specific files. The most critical is the .ops file, which holds the license and authorization information. 

UJAM's file system architecture intentionally separates the small plugin file from its massive .blob content library. This smart design provides the flexibility to store the multi-gigabyte content files on a separate or external hard drive, saving precious space on the main system drive without sacrificing performance. This directly addresses a primary challenge for modern producers: managing large sample libraries on systems with smaller, high-speed primary drives.

UJAM File Locations on macOS

The macOS file system uses two primary Library folders, and UJAM installs components in both, depending on their function. Understanding the difference is key to locating the correct files.

• System Library (/Library/): Located at the root of the main drive (e.g., Macintosh HD/Library/), this folder contains files that are shared among all user accounts on the computer. UJAM installs the plugin executables and, by default, the large .blob content files here to make them accessible system-wide.
• User Library (~/Library/): Located within each user's home folder (e.g., Macintosh HD/Users/USERNAME/Library/), this folder is hidden by default and contains settings and data specific to that user. UJAM stores the critical .ops authorization files and user-saved presets in this location.

Master Directory of UJAM File Locations on macOS

The following table provides a consolidated reference for all default UJAM file paths on the macOS platform.

*The User path is hidden by default by macOS, so use the Go menu with the [option] key to open it.
 

A Note on GarageBand: Why Its Paths Are Different

The unique file paths for GarageBand are not a UJAM-specific setting but a direct result of Apple's security policy known as "sandboxing." Applications distributed through the Mac App Store, like GarageBand, are often sandboxed, which means the operating system isolates them and their data into a secure "container" to prevent them from modifying other parts of the system.

For a UJAM plugin to function correctly within GarageBand, a copy of its necessary support files (like the authorization .ops file) must be placed inside this special container directory. This has a significant implication for troubleshooting: if a plugin works in Logic Pro but fails in GarageBand, the issue may be related to the files within the sandboxed container. When troubleshooting GarageBand-specific issues, it is crucial to check the paths listed in the table above, not the standard UJAM folders.

UJAM File Locations on Windows

On the Windows platform, UJAM utilizes several standard system directories. These are most reliably accessed using their environment variables, which automatically point to the correct location regardless of system configuration.

• %ProgramFiles%: This variable typically points to C:\Program Files and is where UJAM installs plugin files and uninstaller applications.
• %ProgramData%: This variable points to C:\ProgramData, a hidden system folder for application data shared by all users. It is the Windows equivalent of macOS's /Library/Application Support/ and is the default location for the large .blob content files.
• %AppData%: This variable points to a hidden, user-specific folder, typically C:\Users\USERNAME\AppData\Roaming. It is the Windows equivalent of macOS's ~/Library/Application Support/ and is where UJAM stores the .ops authorization files and user-saved presets.

Master Directory of UJAM File Locations on Windows

The following table provides a consolidated reference for all default UJAM file paths on the Windows platform.

VST2 vs. VST3: A Note on Plugin Paths

There is a key difference in how VST2 and VST3 plugin locations are handled on Windows. The older VST2 standard did not enforce a strict installation path, which led to users and installers placing .dll files in many different custom folders. This lack of standardization is a frequent cause of DAWs failing to locate and load VST2 plugins.

To solve this problem, the VST3 standard mandates a single, universal installation path: %ProgramFiles%\Common Files\VST3\. All VST3-compliant installers must use this location, and all VST3-compliant DAWs automatically scan it. This explains why the VST3 path is not customizable. For the most stable and reliable experience, it is recommended to use the VST3 version of a UJAM plugin whenever the host DAW supports it.

Frequently Asked Questions (FAQ)

This section provides step-by-step solutions to the most common file location-related issues.

Q) How do I move the large content (.blob) files to a different drive?

A) The safest and officially recommended method is to use the built-in feature of the UJAM App.

1. Open the UJAM App.
2. Find the product whose content is to be moved.
3. Click the three dots to open the menu and select Move Content.
4. Follow the on-screen prompts to select the new location for the .blob file.

The UJAM App will handle the file transfer and automatically update all necessary settings to ensure the plugin can find its content in the new location.

CRITICAL WARNING for Usynth & Virtual Pianist Users

The Usynth and Virtual Pianist series use a special "frame" architecture. This means there is a main frame .blob file (e.g., USYNTH.blob, VIRTUALPIANIST.blob) and separate title .blob files for each sound library (e.g., USYNTH-DRIVE.blob, VP-VOGUE.blob).

DO NOT MOVE the main frame .blob file. This file contains the core engine and user interface of the plugin and must remain in its default location. Moving it will break the plugin.

Only the individual title .blob files can be safely relocated using the UJAM App.

Some use Symlinking to move the large files out of the OS Drive. If you are interested in that, please check: 

Managing Large .blob Files Using Symbolic Links on macOS

Managing Large .blob Files Using Symbolic Links on Windows

DAW Freeze | exFAT Issues with Usynth and Virtual Pianist (macOS)

Q) My plugin suddenly went back to trial mode! How do I fix it?

A) This issue typically occurs after a significant hardware change to the computer, such as upgrading RAM, swapping a hard drive, or consistently using a new docking station. The UJAM license is tied to a unique "fingerprint" of the computer's hardware. A hardware change can alter this fingerprint, causing the existing .ops license file to become invalid as a security measure.

To resolve this, a new license file must be generated:

1. Close the DAW and the UJAM App completely.
2. Navigate to the user-specific UJAM data folder:

• macOS: ~/Library/Application Support/UJAM/
• Windows: %APPDATA%\UJAM\

3. Inside this folder, find the subfolder for the problematic plugin and delete the .ops file within it (e.g., VD-SOLID.ops).
4. Relaunch the UJAM App (for newer plugins) or open the plugin in the DAW (for older plugins) and follow the prompts to re-authorize online. This will create a new, valid .ops file that matches the current hardware fingerprint.

Q) I can't find the folders you mentioned (Library, AppData, ProgramData). Where are they?

A) Many of the key UJAM folders are hidden by default by the operating system. Here is how to access them.

On macOS (to access ~/Library/):

• Method 1 (Recommended): Open Finder, click the Go menu at the top of the screen, then press and hold the Option (Alt) key. The Library folder will appear in the menu for selection.
• Method 2: Open Finder, click the Go menu, and select Go to Folder... (or press Shift+Command+G). Type ~/Library into the dialog box and click Go.

On Windows (to access %AppData% and %ProgramData%):

• Method 1 (Recommended): Open File Explorer. In the address bar at the top, type %AppData% or %ProgramData% and press Enter. This will navigate directly to the respective folder.
• Method 2: Open File Explorer, click the View tab at the top, and in the "Show/hide" section, check the box for Hidden items. The folders will now be visible in their standard locations (C:\Users\USERNAME\ and C:\).

Q) My DAW isn't showing my new UJAM plugin. What should I do?

A) If a newly installed plugin does not appear in the DAW, follow these troubleshooting steps:

1. Check Compatibility: Ensure the computer's operating system and the DAW version are supported by the plugin.
2. Rescan Plugins: Open the DAW's preferences or plugin manager and trigger a full rescan of all installed plugins. This often forces the DAW to recognize the new addition.
3. Check Scan Paths (VST2 Only): For VST2 plugins on Windows, verify that the DAW's plugin settings include the folder where the UJAM plugin's .dll file was installed. The default is %ProgramFiles%\VSTPlugins\UJAM\.

Q) My plugin loads with a blurred interface or an error message. What's wrong?

A) This symptom almost always indicates that the plugin cannot find its corresponding .blob content file. This commonly happens if the external drive containing the .blob file is disconnected or, on Windows, if its assigned drive letter has changed.

To fix this:

1. Ensure the drive containing the .blob file is connected to the computer and is accessible.
2. Open the UJAM App.
3. Find the problematic plugin, click the three dots to open its menu, and select Locate Content.
4. In the file browser that appears, navigate to and select the correct .blob file to re-establish the link.

Still Need Help?

If the steps in this guide have been followed and issues persist, our support team is here to help. Please submit a request, and we'll get you back to making music.