The error message "Addictive Drums 2 could not find bus layouts" typically indicates a mismatch between the plugin binary location and the expected installation path, or an outdated plugin version being loaded by your DAW. Troubleshooting Steps
To resolve this issue, follow these steps in the XLN Online Installer:
Refresh the Installation: Launch the XLN Online Installer. Often, just opening the application allows it to detect and automatically "miraculously" fix installation hangups. Run a Repair: Open the XLN Online Installer.
Click the "hamburger" menu (three horizontal lines) in the top right corner. Select "Change Installation Formats".
Ensure that the correct versions for your DAW (e.g., VST 2 or VST3) are checked. If they are already checked, you may need to trigger a Repair on the main screen. Verify Plugin Paths:
In the XLN Online Installer, go to Customize Installation and select the Installation Paths tab. addictive drums 2 could not find bus layouts top
Note exactly where the 64-bit VST files are being installed.
Open your DAW (e.g., Ableton, REAPER, or FL Studio) and ensure its VST scan path matches the installer's path.
Update Software: Ensure your DAW is updated to the latest version. A version mismatch (e.g., trying to run a 64-bit plugin in a 32-bit host) can sometimes trigger "bridge" or layout errors. Common Fixes for Specific DAWs
REAPER: If you are getting errors opening older projects, try re-scanning your plugins or checking the "VST 2" box in the XLN Online Installer's installation formats.
Logic Pro: If the plugin fails validation, you may need to delete your AU cache or run the plugin using Rosetta on M1/M2 Macs. The error message "Addictive Drums 2 could not
FL Studio: Use the "Auto map outputs" feature in the Wrapper Settings under the Processing tab to ensure bus layouts are correctly routed.
Are you experiencing this error in a specific DAW or while trying to open a previous project?
.plist file.~/Library/Preferences/ (In Finder, hit Cmd+Shift+G and type that). Delete com.xlnaudio.AddictiveDrums2.plist. Restart.~/Library/Application Support/XLN Audio/Addictive Drums 2/Settings.xml.~/Library/Caches/XLN Audio/Addictive Drums 2/Note:
~/Libraryis hidden by default. In Finder pressCmd+Shift+Gand type~/Libraryto access it.
Before diving into the fixes, you must understand what AD2 is trying to do. A Bus in audio terms is a pathway that carries multiple signals. In Addictive Drums 2, "Bus Layouts" refer to the saved routing configurations that tell the plugin where to send the individual microphones (Kick In, Kick Out, Snare Top, Snare Bottom, Overheads, Room, etc.).
When AD2 cannot find these bus layouts, one of three things has happened: macOS Users
If the above fails, the underlying SQLite database that AD2 uses to remember your busses is corrupted. XLN Audio has a built-in repair tool.
Step-by-Step Resurrection:
This is a last resort. Do not simply uninstall via Windows "Add/Remove Programs." You must delete residual data.
%AppData%\XLN Audio%ProgramFiles%\XLN Audio%ProgramData%\XLN Audio (Windows) or /Library/Application Support/XLN Audio (Mac)Before fixing the problem, you must understand the software architecture of Addictive Drums 2.
Addictive Drums 2 is not just a sample player; it is a sophisticated drum mixer and routing matrix. The "Bus Layouts" refer to the internal routing presets that determine how individual drum microphones (Kick, Snare, Toms, Overheads, Room) are grouped and sent to your DAW’s mixer.
When AD2 "could not find bus layouts top," the plugin cannot locate the master XML or configuration file that tells it how to route audio to your DAW. Essentially, the software is blind. It knows it should have busses, but it does not know where the blueprint for those busses is stored.