Air Music Technology Xpand 2

So You Want to Use Xpand² Without Your Computer Catching Fire

Xpand² is an Air Music Technology virtual instrument that came out around 2010 as a successor to their original Xpand. It's a sample-based multi-timbral workstation plugin, which means it contains thousands of sounds across most instrument categories you'd ever need. Pianos, strings, organs, synths, ethnic instruments, drums. It has them all loaded into one VST/AU/AAX package. The trade-off is that it demands a fair amount of RAM to run properly. The installation process is standard for Mac or Windows. You run the installer, select your plugin format folders, and point it at your DAW's plugin directory. On macOS, make sure the AU bundle is copied to ~/Library/Audio/Plug-Ins/Components. On Windows, the VST2 path is typically something like C:\Program Files\Steinberg\VSTPlugins or wherever your DAW looks. After install, rescan your plugin list. If it doesn't appear, check that you have a valid license key registered. Air uses a simple serial number system, and you can register at their website if you haven't already. I remember loading Xpand² on a 2013 MacBook Pro with 8GB of RAM and immediately noticing how much memory it pulled. It's not unusual for it to take 1.5 to 2GB just sitting there loaded with its default sound. If you're running more than three instances of it alongside a few other large synths, you will run into CPU and RAM pressure. My workaround was to reduce the internal voice count and close any unused tabs. Each active sound category loads its own sample set into memory, so shutting down tabs you're not actually using cuts RAM usage significantly.

How Xpand² Actually Works Under the Hood

The interface is divided into tabs along the top. You've got PIANO, STRINGS, SYNTH, ORGAN, ETHNIC, DRUMS, GUITARS, BRASS, CHOIR, and a few others depending on your version. Each tab contains subcategories of patches. Clicking a patch loads its samples and routing. The main controls below the patch browser are relatively straightforward — filter cutoff, resonance, envelope generators for attack/decay/sustain/release on both amplitude and filter, a simple LFO section, and a basic effects section with reverb, delay, chorus, and distortion. What most people don't realize is that Xpand² is fundamentally a sampled instrument, not a true synthesizer. When you select a patch like "Grand Piano" or "Pad Strings," you're triggering recorded audio samples. The oscillator and filter controls still work, but they're shaping already-recorded waveforms rather than generating them from scratch. This matters because it means the sound has a fixed character at its core, and the knobs only do so much before you're just tweaking further away from the source material. For production work this is usually fine. You're not trying to design a brand-new timbre, you're trying to get a usable piano or string part down quickly.

Common Pitfalls and What to Do Instead

The biggest issue users run into is latency and buffer size. Xpand² sends audio through its internal effects bus, and if your DAW buffer is set too low while running multiple plugin instances, you'll hear phasing artifacts or clicks. I found this out the hard way during a session where I was running three instances of Xpand² alongside a full orchestral library. The phasing between the internal reverb and my DAW's master reverb was causing a subtle comb filtering effect on everything. The fix was simply to bypass the internal reverb on two of the three instances and use my DAW's master reverb instead. Clean signal path, no phase issues. Another thing to watch for is the key-switching behavior. Several of the ethnic and special instrument patches use key-switches to toggle between articulations or modes. If you're programming MIDI data and certain notes seem to do nothing, check the patch documentation. Some patches require you to hit a low C or B before playing the actual melodic range. This isn't intuitive from the interface alone, and the manual is vague about which patches use key-switching. I spent about twenty minutes troubleshooting a non-responsive part before realizing the patch I selected needed a B0 key press to activate the main playing range. The effects section is also where beginners tend to overshoot. The reverb on Xpand² is decent for quick sketches but it starts sounding muddy very quickly past about forty percent mix. Pushing it further introduces a washed-out quality that fights with whatever else is in your mix. Keep the internal effects conservative and let your DAW's mixing environment handle the space.

Performance Tips That Actually Matter

RAM management is the number one concern. Close tabs you aren't actively using. Disable the chorus and delay effects on tracks where they won't be missed. These are small things individually but they add up fast when you have a dense arrangement. I usually keep Xpand² instances limited to two or three in a typical session, and I freeze or bounce any parts I'm done editing to free up processing power. Another thing that helps is using the velocity curve settings. Xpand² lets you adjust how responsive the instrument is to your MIDI controller's velocity. If your playing feels flat or unresponsive, adjust the curve. The default setting favors a moderate response, but if you play hard and your parts sound thin, bumping the curve up makes a noticeable difference in a single adjustment. It took me longer than I'd like to admit to figure this out. For 64-bit DAWs, make sure you're using the 64-bit version of the plugin. Running a 32-bit plugin through a converter adds overhead and can introduce stability issues. Most modern DAWs only support 64-bit plugins anyway, so this is mostly relevant if you're working in an older setup or using a compatibility layer.

Where Xpand² Falls Short

The honest assessment is that Xpand² was built for a different era of music production. It was designed when processors were slower and RAM was expensive, but it hasn't aged gracefully. The sounds lean toward the polished and generic side, and the interface feels cluttered compared to more focused modern instruments. If you need high-quality orchestral samples or realistic pianos, there are much better dedicated options now. Xpand²'s strength was always convenience, not excellence in any single category. It's a Swiss Army knife that does everything adequately but nothing exceptionally well. For people on a tight budget who need a single plugin that covers a wide range of sounds, it still has its place. The preset selection is massive, and having something that works immediately without digging through sample libraries can save time during fast turnaround sessions. But if you're serious about a specific instrument sound, investing in a dedicated tool will pay off. Xpand² is a starting point, not a destination. If you're downloading it, it's available directly from the Air Music Technology website. Make sure you're getting the version that matches your DAW and operating system architecture. The registration process is straightforward, and the download includes both VST2 and VST3 formats along with the AU bundle for Logic and similar hosts.