If you are encountering the error "Could not find BusLayouts specification file!" while trying to load Addictive Drums 2 (AD2),
you are likely facing a common installation path or version conflict issue
. This error typically occurs when the plugin's binary file (DLL or VST) is out of sync with its resource files. Top Fixes for "Could not find BusLayouts" Run the XLN Online Installer Again: Many users report that simply relaunching the XLN Online Installer
and letting it "repair" the installation fixes the missing specification files. Sync Your Plugin Paths: This error often happens if your DAW is loading an old version
file from a different folder while the resources (like bus layouts) are updated elsewhere. Search your PC for all instances of Addictive Drums 2.dll and delete them. Open the Online Installer, go to Customize Installation > Installation Paths , and note the VST 2 (64-bit) Ensure your DAW is only scanning that specific folder. Check for 32-bit vs. 64-bit Conflicts:
If you recently updated to a 64-bit OS (like Windows 11) or a modern DAW, ensure you aren't trying to load the legacy 32-bit version, which may lack current layout files. Why You Can't Find "Bus Layouts" in the Mixer
If your plugin loads but you "could not find bus layouts" to route individual drums to your DAW mixer, follow these steps: Enable Multi-Out Mode: In the AD2 mixer, click the kit piece name at the bottom of a channel (e.g., Kick) and select "Separate Out" Output Types: You can choose "Separate Out Pre-Fader" if you want a dry signal for mixing in your DAW, or "Post-Fader" to keep AD2's internal EQ and compression. DAW Setup:
In DAWs like Reaper or Logic, you must specifically load the "Multi-Output"
version of the plugin (e.g., "16xMono") for these bus layouts to be visible to the DAW's tracks. Interesting Blog Insight: The "Invisible" ID Change
An interesting technical detail often discussed in community blogs (like Cakewalk Forums hardware changes
(like adding RAM) can change your "Computer ID". When this happens, AD2 might partially load but fail to find specific layout or resource files because it thinks the authorization is invalid. The fix is to "Remove Computer" in your XLN Account and re-register via the installer.
This sounds basic, but corrupted temporary cache files can cause the bus layout system to fail. A full restart clears plugin caches.
If the error persists, move to the next step.
The error message is misleading. In the world of VST/AU/AAX plugins, a "bus layout" usually refers to how audio channels are routed (Stereo vs. Surround, Mono vs. Stereo input).
However, in the specific case of Addictive Drums 2, this error is almost exclusively a licensing handshake failure.
AD2 is a ROMpler (Read-Only Memory Player). It doesn't just "run"; it has to check out a license from your system to decrypt its sound library. When the plugin initializes, it performs a rapid-fire series of checks:
If step 1 or 2 fails (due to an outdated license, a corrupted file path, or a background service that hasn't started), the plugin aborts the launch. Because it aborted before it could negotiate the audio routing with the DAW, the DAW reports back: "Could not find bus layouts." It’s the DAW’s way of saying, "I asked the plugin how it wants to output sound, but the plugin didn't answer."
If you are a music producer, beat maker, or sound engineer using Addictive Drums 2 (AD2) by XLN Audio, you may have encountered a frustrating error message:
"Addictive Drums 2 could not find bus layouts. The preset may be corrupt or from a newer version."
Alternatively, some users see a variation: "Could not find bus layouts. Default layout will be used."
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.
Below is a deep-dive into what this error means, why it happens, and, most importantly, how to fix it permanently.
| Step | Action |
|------|--------|
| 1 | Restart the DAW and reload the project. |
| 2 | Remove and re‑add AD2 from the track – some DAWs reload bus layouts on a fresh instance. |
| 3 | Reset AD2 preferences: Delete the user.config or settings.xml inside XLN Audio/Addictive Drums 2/Settings/ (backup first). |
Version mismatch is a leading cause. XLN Audio frequently updates AD2 to support new kits, layouts, and DAWs.
Pro tip: Even if you think you're up to date, run the installer — sometimes minor build updates don't auto-notify.
Features |
Free EditionDownload Freeware |
30-Day License
MBPR-CBV93-OZZPR-OGGKP
Copy
|
Lifetime Upgrade
$35.97
Upgrade with Big Discount
40%
OFF
|
|---|---|---|---|
| License Type | 5 iOS Devices / 1 PC | 5 iOS Devices / 1 PC | |
| Expiration and Upgrade | Valid for 30 Days | Lifetime Use and Free Upgrades | |
| Remove iTunes Backup Encryption | |||
| Unlock iOS Screen Passcode | |||
| Remove Apple ID | |||
| Bypass Screen Time |
If you are encountering the error "Could not find BusLayouts specification file!" while trying to load Addictive Drums 2 (AD2),
you are likely facing a common installation path or version conflict issue
. This error typically occurs when the plugin's binary file (DLL or VST) is out of sync with its resource files. Top Fixes for "Could not find BusLayouts" Run the XLN Online Installer Again: Many users report that simply relaunching the XLN Online Installer
and letting it "repair" the installation fixes the missing specification files. Sync Your Plugin Paths: This error often happens if your DAW is loading an old version
file from a different folder while the resources (like bus layouts) are updated elsewhere. Search your PC for all instances of Addictive Drums 2.dll and delete them. Open the Online Installer, go to Customize Installation > Installation Paths , and note the VST 2 (64-bit) Ensure your DAW is only scanning that specific folder. Check for 32-bit vs. 64-bit Conflicts:
If you recently updated to a 64-bit OS (like Windows 11) or a modern DAW, ensure you aren't trying to load the legacy 32-bit version, which may lack current layout files. Why You Can't Find "Bus Layouts" in the Mixer
If your plugin loads but you "could not find bus layouts" to route individual drums to your DAW mixer, follow these steps: Enable Multi-Out Mode: In the AD2 mixer, click the kit piece name at the bottom of a channel (e.g., Kick) and select "Separate Out" Output Types: You can choose "Separate Out Pre-Fader" if you want a dry signal for mixing in your DAW, or "Post-Fader" to keep AD2's internal EQ and compression. DAW Setup: addictive drums 2 could not find bus layouts
In DAWs like Reaper or Logic, you must specifically load the "Multi-Output"
version of the plugin (e.g., "16xMono") for these bus layouts to be visible to the DAW's tracks. Interesting Blog Insight: The "Invisible" ID Change
An interesting technical detail often discussed in community blogs (like Cakewalk Forums hardware changes
(like adding RAM) can change your "Computer ID". When this happens, AD2 might partially load but fail to find specific layout or resource files because it thinks the authorization is invalid. The fix is to "Remove Computer" in your XLN Account and re-register via the installer.
This sounds basic, but corrupted temporary cache files can cause the bus layout system to fail. A full restart clears plugin caches.
If the error persists, move to the next step. If you are encountering the error "Could not
The error message is misleading. In the world of VST/AU/AAX plugins, a "bus layout" usually refers to how audio channels are routed (Stereo vs. Surround, Mono vs. Stereo input).
However, in the specific case of Addictive Drums 2, this error is almost exclusively a licensing handshake failure.
AD2 is a ROMpler (Read-Only Memory Player). It doesn't just "run"; it has to check out a license from your system to decrypt its sound library. When the plugin initializes, it performs a rapid-fire series of checks:
If step 1 or 2 fails (due to an outdated license, a corrupted file path, or a background service that hasn't started), the plugin aborts the launch. Because it aborted before it could negotiate the audio routing with the DAW, the DAW reports back: "Could not find bus layouts." It’s the DAW’s way of saying, "I asked the plugin how it wants to output sound, but the plugin didn't answer."
If you are a music producer, beat maker, or sound engineer using Addictive Drums 2 (AD2) by XLN Audio, you may have encountered a frustrating error message:
"Addictive Drums 2 could not find bus layouts. The preset may be corrupt or from a newer version." This sounds basic, but corrupted temporary cache files
Alternatively, some users see a variation: "Could not find bus layouts. Default layout will be used."
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.
Below is a deep-dive into what this error means, why it happens, and, most importantly, how to fix it permanently.
| Step | Action |
|------|--------|
| 1 | Restart the DAW and reload the project. |
| 2 | Remove and re‑add AD2 from the track – some DAWs reload bus layouts on a fresh instance. |
| 3 | Reset AD2 preferences: Delete the user.config or settings.xml inside XLN Audio/Addictive Drums 2/Settings/ (backup first). |
Version mismatch is a leading cause. XLN Audio frequently updates AD2 to support new kits, layouts, and DAWs.
Pro tip: Even if you think you're up to date, run the installer — sometimes minor build updates don't auto-notify.
90-Day Unconditional
Money Back Guarantee
License Code
Instant Delivery
Perpetual Free
Technical Support
256-Bit SSL
Secure Order