Do I really need the UJAM App?

For the majority of the current UJAM product line, the UJAM App is not optional software; it is a required dependency for licensing and content management.

Whether you need the app depends entirely on the plugin architecture of the products you own, defined as Type 1 or Type 2 plugins.

1. Architecture & Dependencies

Type 1 Plugins: Headless Architecture (App MANDATORY)

Type 1 plugins are designed with a "headless" licensing structure. They do not contain the code libraries required to render a login GUI within the DAW. Instead, they rely on an external inter-process communication (IPC) call to the UJAM App to verify the validity of the local license token.

• Status: Mandatory Dependency. The plugin will fail to initialize or remain in Trial Mode without the UJAM App running as a background service.
• Affected Products (Frame & Standalone):

• Usynth Series (All titles)
• Virtual Pianist Series (All titles)
• BeatMaker 3 Series (IDOL, GLORY, KANDY, NEMESIS, VICE, COZY, etc.)
• UFX Series (REVERB, DELAY)
• Subcraft

Type 2 Plugins: Legacy GUI Architecture (App Recommended)

Type 2 plugins contain legacy authorization code allowing for direct credentials input (Email/Password) via the plugin interface. These plugins generate the hardware fingerprint locally without needing the UJAM App's IPC bridge.

• Status: Optional, but the UJAM App is recommended for .ops file integrity checks and updates.
• Affected Products:

• Virtual Guitarist Series ( e.g. IRON, SPARKLE, AMBER, SILK, CARBON)
• Virtual Drummer Series
• Finisher Series
• Virtual Bassist Series

2. Technical Capabilities & System Integration

The UJAM App functions as a background daemon that handles file operations and server synchronization. It is designed to be non-blocking and resource-efficient, consuming negligible CPU cycles as it does not perform audio signal processing.

A. Authorization Subsystem (.ops Management)

UJAM authorization relies on .ops files. These are encrypted JSON-like files containing a hardware fingerprint (based on CPU ID, Logic Board Serial, and Network Interface MAC address).

• The App's Role: It queries the UJAM License Server API to retrieve a signed token, then generates the machine-specific .ops file.
• Hardware Changes: If hardware changes (e.g., new Network Adapter), the fingerprint breaks. The UJAM App detects this mismatch and silently regenerates the .ops file in the background, preventing license invalidation.
• File Paths:

• Windows: %APPDATA%\Roaming\UJAM\<PluginName>\
• macOS: ~/Library/Application Support/UJAM/

B. VST/AU/AAX Dependency Management

The App enforces strict directory compliance, particularly for the VST3 standard, which mandates installation to %ProgramFiles%\Common Files\VST3\ (Windows) or /Library/Audio/Plug-Ins/VST3/ (macOS).

• Content Linking: Large sample libraries are stored in .blob files. The App manages the link between the plugin DLL/VST3 and the external content drive. If content is moved, the "Locate Content" function in the App updates these pointers in the system registry or plist files.

C. Version Control

The App performs checksum verifications against the latest stable builds on the UJAM Content Delivery Network (CDN). It ensures plugins are patched against known DAW-specific bugs (e.g., Logic Pro validation failures or Studio One OpenGL conflicts).

3. Protocol: Single Credential Set

Critical Requirement: You must use one single email account for all UJAM plugins.

The UJAM App and plugins share a local license database (_PluginDatabase.dat or similar internal cache). Mixing credentials (e.g., authorizing Plugin A with email_X and Plugin B with email_Y) causes database corruption known as an Authorization Loop.

• Symptom: Plugins revert to "Trial Mode" immediately after activation.
• Resolution: Requires manual deletion of all .ops files and a full cache flush.
• Reference: See One Single Email Account for UJAM for protocol enforcement.

4. FAQ Reference

For specific error codes (e.g., "Internet Connection Required"), firewall port configurations, or advanced troubleshooting regarding the app's background processes, please refer to the technical documentation here:

• FAQ | UJAM App

Summary Data