What does the USB cable actually carry?
Your module sends MIDI, not sound. Each hit becomes a tiny message: which pad or zone was struck, as a note number, and how hard, as a velocity from 1 to 127. The snare head, its rim and a cross-stick are different note numbers; so are the bow, the edge and the bell of a ride. That is all a drum game needs, and it is what WebEDrums reads through the browser's Web MIDI interface.
The drum sounds you hear stay in the module unless you decide otherwise. Some modules can also send audio over the same cable (the Roland TD-02 in its Vendor mode, the Yamaha DTX402 and DTX-PRO), but that is a separate feature with its own driver on Windows, and nothing in this guide depends on it.
Which port and cable do I need?
- The module's USB port. It is usually a square USB-B socket, labelled USB COMPUTER on Roland modules, USB TO HOST on Yamaha modules, and USB or USB/MIDI on Alesis modules.
- A data cable. Use a USB-A to USB-B cable that carries data, not a charge-only cable; Roland and Yamaha both make this point in their support pages. A USB-C to USB-B cable or a small adapter is fine for a laptop without USB-A. Yamaha asks for a cable under 3 metres.
- No hub if you can avoid it. The Clone Hero wiki traces most "nothing registers" reports to USB power and suggests another port or a powered hub.
- Only a 5-pin MIDI OUT socket? A MIDI-to-USB interface turns it into a USB MIDI device. The YARG wiki notes that kits with only 5-pin DIN output need such an adapter, and that it supports them.
- Bluetooth on most modules is for streaming music into the module. Alesis documents the Nitro Max's Bluetooth as audio streaming, and Roland sells the TD-02's wireless adaptor separately. Use the cable for the kit's notes.
Do I need to install a driver?
For MIDI, almost never. The common modules are class compliant: the operating system already has the driver.
- Alesis says the Nitro Mesh and Nitro Max modules are class compliant and work with any modern Mac or PC without downloading software or drivers, and that their USB connection carries MIDI only.
- Yamaha's computer-connection guide says that for MIDI the standard drivers of Windows and macOS are enough and no other driver is needed; the Yamaha Steinberg USB Driver is for audio over USB on Windows.
- Roland's TD-02 has two USB driver modes: Generic, which uses the operating system's own driver and carries MIDI only, and Vendor, which needs Roland's TD-02 driver and adds USB audio. For a drum game, Generic is enough. Vendor mode carries MIDI as well, so a module already set up for recording needs no change.
A maker's driver is only ever about audio over USB; it is never the reason a kit is not seen.
How do I connect the kit to a laptop, step by step?
- Plug the cable in. Connect a USB data cable to the module’s USB port (USB, USB COMPUTER or USB TO HOST), then to the computer. Yamaha suggests connecting the cable before switching the module on.
- Switch the module on. Turn the module on. On Windows, close any other program that could be using it, such as a recording program or the maker’s editor app: Windows hands a MIDI device to one program at a time.
- Open the software. Open the program that will read the kit. For WebEDrums, open webedrums.com/app/ in Chrome or Edge, click Drums setup, then the E-drum kit card.
- Allow MIDI access. Chrome and Edge ask once for permission to use MIDI devices; click Allow. Firefox 108 and newer asks you to install a small site-permission add-on instead; accept it. Safari has no Web MIDI.
- Hit a pad. Strike the snare. The software should react at once; WebEDrums shows the module’s name and reports it as connected. If nothing happens, work through the checklist below.
- Tell the software which pad is which. Map the pads. WebEDrums recognises Roland, Alesis and Yamaha modules from their USB name and offers that preset; otherwise its guided setup asks you to hit each pad in turn and records every zone it hears. Clone Hero and YARG have their own mapping screens.
What if the kit does not show up?
For WebEDrums, the kit connection FAQ shows every step with screenshots, and the fixes for Chrome, Edge, Firefox and Safari.
- Check the cable first. A charge-only USB-C cable is the most common cause of a module that powers up but never appears.
- Try another port, and no hub. If it must be a hub, use a powered one. On Windows the Clone Hero wiki also suggests turning off USB selective suspend in the power settings and trying a USB 2.0 port instead of a 3.0 one, or the other way round.
- Close other MIDI programs on Windows. The YARG wiki puts it plainly: Windows only allows one program to access a MIDI device at a time. A browser tab that already holds the kit counts as a program.
- Look at the browser's site permission. If you clicked Block once, Chrome and Edge remember it. Open the site information icon left of the address bar, allow MIDI, then reload the page.
- Firefox needs its site-permission add-on installed. It also cannot remember the songs folder between visits, so Chrome or Edge is the easier choice for WebEDrums.
- Still nothing? The Clone Hero wiki recommends a MIDI monitor program on the computer. If the monitor shows notes arriving, the problem is in the game's device list; if it shows nothing, it is the cable, the port or the module.
How do I hear the song and the drums together?
Two setups work; here is a diagram of each.
Drum sounds from your module
Keep your kit's own sounds, with no browser delay. WebEDrums plays only the song: join the computer's audio and the module's headphone or output jack with a splitter cable or a small mixer, and plug that into the speaker.
Drum sounds from WebEDrums
For when the module is muted or has no audio output. Turn on "Kit sounds in the browser" in Settings and WebEDrums plays the song and a synthesised kit through the computer's speaker or headphones. It adds a little latency, so run the timing calibration once.
- Drum sounds from the module, no delay. The computer plays the song, the module plays the kit. Join the two with a splitter cable or a small mixer into one speaker or pair of headphones, or feed the computer's headphone output into the module's audio input (MIX IN on the Roland TD-02, AUX IN on the Yamaha DTX402, the Aux input on the Alesis Nitro Max) and listen on the module's phones jack. The kit's own sounds never pass through the computer, so they cannot lag.
- Drum sounds from the software. For a muted module, or one with no output, the software can play a kit of its own. Any software kit adds a few milliseconds of audio buffering. WebEDrums calls this setting "Kit sounds in the browser" and asks you to run its six-second timing calibration afterwards, so that hits are judged against what you actually heard.
Headphones on the module remain the simplest low-latency option; the YARG wiki recommends headphones over speakers for the same reason.
Does this work on a Chromebook?
Yes, in Chrome. Chrome on ChromeOS has Web MIDI, so the steps are the same: cable in, allow MIDI, hit a pad. WebEDrums reads its songs from a folder or a zip on the Chromebook. Clone Hero and YARG are desktop downloads with no ChromeOS build; whether Clone Hero's Android version runs on a given Chromebook, and sees a USB kit there, is not something the project states.
Sources
Checked on October 16, 2026. If one of these pages has changed and this guide has not caught up, tell us on the contact page.
- Clone Hero wiki: Drum Mapping Guide
- Clone Hero wiki: Drum FAQs and Troubleshooting
- YARG wiki: Hardware compatibility
- YARG wiki: Troubleshooting instruments
- YARG wiki: Calibration
- Alesis: Nitro Mesh Kit frequently asked questions
- Alesis: Nitro Max Kit frequently asked questions
- Roland: TD-02KV product page and specifications
- Yamaha: DTX402 series specifications
- Chrome for Developers: Web MIDI permission prompt
- Firefox 108.0 release notes