Plugging an electronic drum kit into a computer opens a lot of doors. You can play through drum software that sounds better than the module, use lesson apps, record practice sessions and make full songs. The cable is the easy part. The confusion starts after that: does the kit send audio or only MIDI, which driver does it need, why is there a delay, and why does the hi-hat sound wrong in the software?
This guide takes you through the connection step by step. It is based on manufacturer manuals and support pages from Roland, Yamaha, Alesis and Simmons, plus the problems owners raise most often. Exact menu names differ by model, so keep your manual handy.
Short answer
What you need
- The kit’s module, with a USB port labeled for a computer (often USB-B, sometimes USB-C on newer modules).
- A USB cable that matches. Kits do not always include one. Use a cable meant for data, not just charging.
- A computer running Windows or macOS. A tablet works too for lessons and some music apps.
- Software: a DAW (recording program) such as GarageBand, Logic Pro, Reaper, Ableton Live or Cubase, and optionally drum software (a VST or AU plugin).
- Headphones, ideally plugged into the source you will be listening through.
You may also need an audio interface if your kit does not send audio over USB and you want to record the module’s own sound. More on that below.
USB MIDI vs USB audio: the most important difference
These two terms cause most of the confusion, so it is worth understanding them before you plug anything in.
USB MIDI
MIDI is not sound. It is a stream of instructions: which pad was hit, how hard, and when. When your kit sends MIDI to a computer, the computer has to make the sound itself using drum software. The kit’s own module sounds are not sent.
Almost every modern kit supports USB MIDI. It is what you need for drum software, lesson apps like Melodics, and recording drum parts you can edit later.
USB audio
USB audio sends the actual sound from the module, the same sound you hear in your headphones, to the computer as digital audio. You can record it directly, without an audio interface.
Not every kit has this. Many Roland kits (including the TD-02KV and TD-07 series), the Simmons Titan 50 and EFNote kits do. Some popular beginner kits, including the Alesis Nitro Max, send only MIDI over USB. On those kits, if you want to record the module’s sound, you connect its audio outputs to an audio interface instead.
Higher-end modules can send several audio channels over USB, such as kick, snare and toms on separate tracks. That is mainly useful for recording and mixing, which I cover in how to record electronic drums.
| Feature | USB MIDI | USB audio |
|---|---|---|
| What it sends | Hit data (note, velocity, time) | The module’s actual sound |
| Needs drum software to hear | Yes | No |
| Editable after recording | Fully (notes, timing, sounds) | Only as audio |
| Typical driver need | Usually none | Often a maker’s driver on Windows |
| Common on | Almost all kits | Many mid-level and some beginner kits |
Many kits send both at the same time over one cable, which is useful.
Step 1: Connect the cable
Find the port marked “USB COMPUTER,” “TO HOST” or similar. Do not use a USB-A port on the module. That port is usually for a flash drive, for loading samples or saving backups.
Connect directly to a USB port on your computer if you can. USB hubs, especially unpowered ones, cause dropouts and devices that disappear. If you must use a hub, use a powered one.
Turn on the module after the cable is connected, or follow the order your manual recommends.
Generic mode vs vendor mode
Some modules have a USB driver mode setting, and it decides what you get. Roland is the clearest example. Roland’s spec sheet for the TD-02 says USB audio only works in vendor mode with Roland’s driver installed. In generic mode you get MIDI only. The V51 module in the TD516 sends 2 channels each way in generic mode and up to 32 channels in vendor mode. If your Roland kit shows up as MIDI but not as an audio device, this setting is the first thing to check, on Mac as well as Windows.
Step 2: Install drivers if needed
Mac
Macs handle most USB MIDI and many USB audio devices without extra drivers, because they follow a “class compliant” standard. Open Audio MIDI Setup (in Applications, Utilities) and look for the kit under the MIDI Studio and Audio Devices windows. If it shows up in both, you are set.
Some modules still need a driver on the Mac for full audio features, including Roland modules in vendor mode. Check the support page for your model.
Windows
Windows usually recognizes USB MIDI without a driver. USB audio is different. To get low latency on Windows, programs use a driver standard called ASIO. Most drum module makers that offer USB audio publish an ASIO driver for their modules. Roland and Yamaha both have driver downloads on their support pages, listed by model.
Install the driver before connecting the kit, then restart if asked. Then check Device Manager or your DAW’s audio settings to make sure the kit appears.
If your kit has no ASIO driver and you only use MIDI, you can use your computer’s built-in sound with a generic low-latency driver such as ASIO4ALL or FlexASIO. A dedicated audio interface with its own driver gives the most reliable results.
Firmware
Before you troubleshoot drivers, update the module’s firmware. Some connection problems are fixed in firmware updates.
Step 3: Set up your DAW
Every DAW has the same basic setup. Look for the audio and MIDI settings, usually under Preferences or Settings.
Audio device. Choose the device you will hear sound through. If you use drum software, that is your audio interface, the module (if it has USB audio), or the computer’s built-in output. On Windows, choose the ASIO driver for that device.
MIDI input. Turn on the kit as a MIDI input. In some DAWs this is in the preferences, in others on each track.
Create a track. For MIDI, create an instrument track and load drum software on it. For audio from the module, create an audio track with the module’s USB input selected.
Arm and monitor. Arm the track for recording and turn on input monitoring, so you hear the drum software when you hit the pads.
If you hit a pad and see a MIDI meter move but hear nothing, the MIDI is arriving, and the issue is the audio output or the instrument on the track.
Step 4: Set up drum software
Drum software, called VST plugins on Windows and AU or VST on Mac, turns MIDI from your kit into high-quality drum sounds. There are free options and paid libraries with very detailed sampled kits. My guide to the best drum VST plugins compares them.
Pick a drum map
Each kit sends specific MIDI note numbers for each pad. Drum software expects certain notes for each drum. If they do not match, hitting the snare might play a tom.
Many kits follow the General MIDI drum map for basic pads. Common notes include:
| Pad | Common GM note |
|---|---|
| Kick | 36 |
| Snare | 38 |
| Closed hi-hat | 42 |
| Pedal hi-hat | 44 |
| Open hi-hat | 46 |
| Crash | 49 |
| Ride | 51 |
Rims, hi-hat zones, cymbal bells and extra toms vary by brand. Most drum software includes ready-made maps for Roland, Yamaha, Alesis and other modules. Pick the map that matches your kit. If there is none, use the software’s MIDI learn function: hit each pad and assign it.
The hi-hat needs extra attention
Hi-hats are where most mapping problems appear. Besides notes, the kit sends a continuous message for how open the hi-hat is. Many kits send this as MIDI control change 4 (CC4). The drum software uses it to choose between closed, half-open and open sounds.
If the hi-hat always sounds open or closed in your software, check that the software is set to receive CC4 (or whatever your kit uses) and that the range matches. Some software lets you set the open and closed points to match your controller.
Mute the module’s own sound
When you play through drum software, you might hear both the module’s sounds and the software sounds at once. Turn down the module’s volume, use headphones on the computer side, or turn off “local control” if your module has that setting. That way you only hear the software.
Step 5: Reduce latency
Latency is the delay between hitting a pad and hearing the sound. Drums are all attack, so a delay is easier to notice than on a pad synth or a slow string sound. There is no single number everyone agrees on. My rule of thumb is to keep the total your DAW reports under about 10 milliseconds and go lower if you can.
Buffer size
The main setting is the audio buffer size, set in your DAW or driver control panel. A smaller buffer means less delay but more work for your computer.
You can work out the one-way buffer delay: buffer size divided by sample rate. At 48 kHz:
| Buffer | Delay for that buffer |
|---|---|
| 64 samples | about 1.3 ms |
| 128 samples | about 2.7 ms |
| 256 samples | about 5.3 ms |
| 512 samples | about 10.7 ms |
The real total is higher, because input and output each add a buffer plus driver and converter delays. That is why your DAW may report a larger number. A good starting point for playing drums live through software is 128 samples, then try 64 if your computer handles it without clicks.
Other latency fixes
- Use a proper driver. On Windows, ASIO drivers give much lower latency than the default Windows audio drivers.
- Close other programs. Browsers and video apps compete for processing power.
- Use simpler drum presets while playing. Heavy reverbs and room mics add load. Turn them on for mixing instead.
- Freeze or bounce other tracks. If you are playing over a busy song, render other instruments to audio.
- Avoid Bluetooth. Bluetooth headphones and Bluetooth MIDI add noticeable delay. Use wired connections for playing.
- Plug directly into the computer. Avoid hubs and long USB extension cables.
If latency is still a problem, you can practice using the module’s own sound in your headphones and use the computer only for recording MIDI. That gives you zero added delay while playing.
Connecting to a tablet or phone
Many kits work with tablets for lesson apps and simple recording. For an iPad or iPhone with USB-C, connect the kit with a USB-C cable that matches the module’s port. Older Lightning devices need Apple’s camera adapter. Class-compliant modules are recognized by iOS without drivers.
Android support varies by phone and app. Test with a free MIDI monitor app before buying paid apps.
Bluetooth MIDI is built into several kits, such as the Roland TD-07 series and the Simmons Titan 50. The TD-02 needs Roland’s optional BT-DUAL adapter for it. Bluetooth is convenient for lessons. For recording, use USB.
Older kits without USB
Some older modules have only 5-pin MIDI ports. To connect them, you need a USB-to-MIDI interface. Connect the module’s MIDI OUT to the interface’s MIDI IN, then plug the interface into the computer. The cheapest no-name cable interfaces are the usual suspect when notes go missing, so if you see dropouts, try a MIDI interface from an established audio brand before blaming the module.
To record the module’s sound, use its audio outputs into an audio interface. The audio interface guide covers what to look for.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| Computer does not see the kit | Wrong port, charge-only cable, hub | Use the “to computer” port, a data cable, connect directly |
| MIDI meter moves, no sound | No instrument or wrong audio output | Load drum software, check audio device and track output |
| Wrong drums play | Drum map mismatch | Choose your module’s map or use MIDI learn |
| Hi-hat always open or closed | CC4 not received or range wrong | Enable hi-hat controller input, adjust range |
| Double sounds | Module and software both playing | Turn down the module or use local control off |
| Delay when playing | Buffer too large, wrong driver | Lower buffer, use ASIO on Windows |
| Clicks and pops | Buffer too small, CPU overloaded | Raise buffer one step, close apps |
| Kit disappears during session | USB power saving, loose cable | Turn off USB power saving, secure the cable |
Bottom line
Use the module’s computer port, install the maker’s driver if you need USB audio on Windows, set up your DAW with the kit as a MIDI input, choose the right drum map and keep the buffer small. Get those steps right and your kit becomes a full recording and practice tool. If you are still choosing a kit and recording matters, my guide to the best electronic drum kits for recording looks at USB audio and outputs in detail.
FAQ
Do electronic drums need an audio interface to connect to a computer?
Not usually. USB MIDI works without one, and many kits also send audio over USB. You need an interface when the kit sends only MIDI over USB and you want to record the module's own sound, or when you want better latency on a computer without good drivers.
Why does my Roland kit show up as MIDI but not as an audio device?
The module is probably in generic USB mode. On kits like the TD-02, USB audio needs vendor mode plus Roland's driver, which you download from the model's support page. Switch the mode in the module's setup menu, restart the module, and the audio device should appear.
Why is there a delay when I play drums through my computer?
That is latency, mostly caused by the audio buffer size. Lower it to 128 or 64 samples, use an ASIO driver on Windows, and avoid Bluetooth headphones. If the delay remains, monitor the module directly and record MIDI in the background.
Does the Alesis Nitro Max send audio over USB?
No. The Nitro Max sends MIDI over USB. To record its built-in sounds, connect its main outputs to an audio interface. To use better sounds, play drum software from its MIDI signal.
Which free software can I use with electronic drums?
GarageBand on a Mac has a drum kit instrument that works with USB MIDI. Several free drum plugins exist for Windows and Mac, and some kits bundle drum software: Alesis includes BFD Player with the Nitro Max. Reaper is an affordable DAW with a long trial period.
How do I connect electronic drums to an iPad?
Use a cable from the module's USB port to the iPad's USB-C port, or Apple's camera adapter on older Lightning models. Class-compliant modules work without drivers. Some kits also support Bluetooth MIDI for lesson apps.