Once completed, open your DAW and try loading the plugin again. If the error persists, move to the platform-specific steps below. Step 2: Fix macOS Permissions and Sandbox Issues
Work through the following solutions in order. The first method is the most likely to solve the problem.
When the plugin engine initialises, it expects to find this file in a relative path. If it cannot find it, it throws a fatal std::runtime_error exception. The most common causes are:
for each drum piece. In version 2.6 and later, you can select "Route All Channels" for a faster setup. DAW Side Configuration : In your DAW mixer, click the icon on the plugin track (Logic) or use "Auto map outputs" addictive drums 2 could not find bus layouts
If the plugin loads but you cannot find the actual bus layout for separate outputs:
Wait for the installation to finish and restart your computer. Step 2: Refresh the Resource Folders
This error typically appears when loading a kit preset, a beat, or even when opening an existing project in your Digital Audio Workstation (DAW). It can halt your workflow, reset your mixer routing, or even mute individual drum channels. Once completed, open your DAW and try loading
Outdated plugin software trying to read newer library files. Incorrect installation paths or broken file directories. Missing administrative permissions during installation. Corrupted cache files in the XLN Online Installer. Step-by-Step Solutions 1. Run the XLN Online Installer (The Quickest Fix)
Check the path indicated in the XLN Online Installer under "Installation paths" -> "VST 2 (64-bit)". 4. Force a Re-scan in Your DAW
If you are reading this, you have likely just dropped XLN Audio’s Addictive Drums 2 (AD2) into a MIDI track, expecting the familiar saturation of a compressed snare, only to be met with a cold, cryptic error: The first method is the most likely to solve the problem
Go to System Settings > Privacy & Security > Full Disk Access. Ensure your DAW (Logic, Ableton, etc.) is toggled "On." Step 4: Relocate the "Settings" Folder
To help narrow down the quickest solution for your specific setup, please let me know:
Click the button (often a gear icon or a link at the bottom).
Step 4: Manually Verify the AppData / Application Support Folder
Right-click your DAW icon (e.g., Reaper, Cubase, Studio One) and select "Run as Administrator." If Addictive Drums 2 loads perfectly now, the issue is strictly related to Windows user account permissions.