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.
Check the BusLayouts folder existence:
C:\Users\[YourUsername]\Documents\XLN Audio\Addictive Drums 2\BusLayouts\~/Documents/XLN Audio/Addictive Drums 2/BusLayouts/Default.adbus, Stereo.adbus, Multi.adbus, etc.Verify file integrity:
Examine DAW’s plugin wrapper logs (if available) – look for “bus layout parse error”.
Test in a different DAW – if error persists, the problem lies in AD2’s data folder or permissions. If error disappears, the issue is DAW‑specific caching.
Logs/).The studio was dimly lit, the only source of light being the neon-blue hum of a dual-monitor setup. Marcus had been sitting in the same ergonomic chair for six hours, fueled by lukewarm coffee and the desperate need to finish a drum track for a client whose deadline was "yesterday."
He opened his session in REAPER, ready to drop in a heavy rock kit. But when he clicked to load Addictive Drums 2, the familiar interface didn't appear. Instead, a cold, clinical error message flickered on the screen:
"createPluginFilter exception: Could not find BusLayouts specification file!" The Vanishing Act
Marcus stared at the screen, his heart sinking. He had used this plugin thousands of times, but now it acted like it had forgotten how to exist. It was as if the "map" the software used to route sound—the BusLayouts—had simply vanished into the digital ether.
He tried the classic move: closing the DAW and restarting his computer. Nothing. He checked his VST paths, half-hoping the .dll file had just gone for a walk to a different folder. He even considered that his recent RAM upgrade had somehow de-authorized his machine, a common ghost in the machine for XLN Audio users. The Digital Repair
Desperation led him to the XLN Online Installer. This was the master control, the place where digital logic lived. Following advice from a Cakewalk forum thread from nearly a decade ago, he opened the "Advanced" tab. addictive drums 2 could not find bus layouts
Locate the Ghost: He used the installer to repair his installation, forcing the software to re-scan for that elusive BusLayouts file.
Clear the Path: He realized that an old 32-bit version of the plugin was clashing with the modern 64-bit environment of his new OS.
The Re-link: He manually pointed the installer to his VST2 folder, ensuring the Addictive Drums 2.dll was exactly where the DAW expected to find it. Back to the Beat
With a final click of "Apply," Marcus held his breath and re-opened his session. He clicked the plugin slot. This time, the familiar grey-and-orange interface of Addictive Drums 2 filled the screen, the Fairfax Vol. 1 kit ready and waiting.
The "BusLayouts" weren't lost; they were just waiting for him to remind the computer where home was. He hit "Record," and the room finally filled with the sound of a snare drum that didn't just sound like a kit—it sounded like victory. problems loading Addictive Drums - Cakewalk Forums
The error "Could not find BusLayouts" in Addictive Drums 2 (AD2) typically indicates a mismatch between the plugin binary location and its resource files, often caused by a corrupted installation or an outdated plugin version being scanned by your DAW. Incident Summary
Error Message: createPluginFilter exception: Could not find BusLayouts specification file!.
Root Cause: This usually occurs when the DAW tries to load an old or misplaced .dll or .vst file that cannot find its associated support files. It is also common in non-standard environments, such as Linux/Wine setups, where file path mapping may fail. Resolution Steps Run a Repair Install: Open the XLN Online Installer.
Select Addictive Drums 2 and choose the Repair or Update option. This forces the installer to verify all necessary specification files, including bus layouts. Clean Up Duplicate Plugin Files:
Search your computer for all instances of Addictive Drums 2.dll or Addictive Drums 2.vst3.
Delete all copies manually to ensure your DAW isn't accidentally loading an orphaned, older version.
Run the XLN Online Installer again to place a fresh, correctly linked version in your designated VST folder. Verify File Paths:
In the XLN Online Installer, go to Advanced or Customize Installation to confirm the "Installation Path".
Ensure your DAW's VST preferences are pointed specifically to that folder and perform a Full Rescan. Environment-Specific Fixes: Fixing the "Addictive Drums 2 Could Not Find
Windows/Mac: Ensure you aren't trying to run a 32-bit plugin in a 64-bit DAW (or vice versa), as bridging issues can trigger layout errors.
Linux (Wine/Lutris): If you are using Linux, users have reported that launching via Lutris can resolve "BusLayouts" errors by correctly setting up the necessary DLL overrides.
For further assistance, you can refer to the official XLN Audio Support page or contact their team directly.
You can force AD2 to revert to its built-in stereo bus layout.
Now close and reopen your project. The error should stop appearing.
The “could not find bus layouts” error is almost always solvable without data loss. In 90% of cases, resetting AD2’s preferences or restoring the BusLayouts folder resolves the issue. If the problem persists after following sections 5.1–5.4, a clean reinstall is recommended. For further assistance, contact XLN Audio support with a copy of your diagnostics.log (found in the AD2 data folder).
Appendix A – Support ticket template
Include: OS version, DAW & version, AD2 version, steps already taken from this report, and a screenshot of the error.
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.
The "Could not find BusLayouts specification file!" error in Addictive Drums 2 (AD2) typically stems from a corrupted installation or an environment that prevents the plugin from locating its core configuration files. Immediate Fixes
Re-run the XLN Online Installer: In many cases, simply relaunching the XLN Online Installer and letting it complete its initial boot sequence fixes the issue. Repair the Installation: Open the XLN Online Installer. Click the hamburger menu in the top right.
Select "Change Installation Formats" and ensure your required formats (e.g., VST 2, VST 3, AU) are checked.
Click Repair on the next screen to force a refresh of missing specification files.
Verify VST Paths: Ensure your DAW is scanning the exact folder where AD2 is installed. You can find your current installation path by clicking "Customize Installation" > "Installation Paths" within the XLN Online Installer. Troubleshooting Common DAW Routing
If the plugin loads but you cannot find the actual bus layout for separate outputs:
Enable Separate Outs: Within the AD2 interface (Kit or Edit page), you must click the small arrow [↓] at the bottom of each channel fader to activate the output. DAW-Specific Multi-Out:
Logic Pro: You must load AD2 as a Multi-Output instrument from the start; otherwise, the auxiliary channels for bus layouts will not be available.
Reaper: Use Insert > Virtual Instrument on New Track to let Reaper automatically build the 18-channel routing for you.
FL Studio: In the wrapper's Processing tab, click "Auto map outputs" to link AD2's internal buses to mixer tracks. Environmental Hurdles
Linux Users: This error is common when running the installer through Wine/ProAudio environments. Running the installer through Lutris has been reported to resolve the "BusLayouts" exception due to its automated DLL configuration.
Windows Permissions: Ensure the VST folder is excluded from Windows Defender or antivirus scans, as these can sometimes block the plugin from reading its specification files.