How does the Alesis Nitro connect to a computer?
Over USB. Alesis describes both the Nitro Mesh and the Nitro Max module as class compliant: the module "will work with any modern Mac or PC" without downloading software or drivers. Alesis is also clear about what the cable carries: the USB and the 5-pin MIDI connections pass MIDI information only, never audio, so the kit's sounds stay on the module's outputs and headphone jack. Use a USB-A to USB-B data cable, with a USB-C adapter if the computer has no USB-A port.
The Nitro Max adds Bluetooth, but Alesis documents it as audio streaming into the module (your phone's music in your headphones), not as a MIDI link; the computer connection stays USB. On Windows, one program at a time can hold the module: close Melodics, Drumeo, BFD Player or a recording program before opening the browser, and close the browser tab before going back to them.
Which preset do I pick in WebEDrums?
WebEDrums reads the name the module gives over USB. When it contains Alesis, Nitro, Strike, Surge or Crimson, the kit setup page offers "Use Alesis defaults instead", which loads the table below in one click. If your module reports a generic name, run the guided setup: it asks for each pad in turn, records every zone you hit within a second and a half, and works for any kit. Either way you review each pad's lane before saving, and you can come back through Settings, Kit, Edit mapping.
The General MIDI preset covers the same notes apart from the floor tom's rim (58), so a module detected as generic still plays every head correctly; the Alesis defaults just add that one rim.
Which pads and zones does the Alesis preset map?
This table is generated from the preset inside the app, so it is what WebEDrums listens for when you choose the Alesis defaults. Several notes end up on one lane on purpose: the games have one red lane, not a head and a rim.
| Pad | Notes the preset listens for | Plays as |
|---|---|---|
| Kick | 36 head | Kick |
| Snare | 38 head · 40 rim · 37 cross-stick | Red (snare) |
| Hi-hat | 46 bow · 42 bow | Yellow cymbal |
| Tom 1 (high) | 48 head · 50 rim | Yellow tom |
| Tom 2 (mid) | 45 head · 47 rim | Blue tom |
| Floor tom | 43 head · 58 rim | Green tom |
| Crash | 49 bow · 55 edge | Green cymbal |
| Ride | 51 bow · 53 bell · 59 edge | Blue cymbal |
| Crash 2 (optional) | 57 bow · 52 edge | Green cymbal |
- Snare head, rim and cross-stick all play the red lane, and the hi-hat's open and closed notes both play the yellow cymbal, which is what every drum chart expects.
- Whether a tom on your model has a rim zone depends on the kit; the preset simply lists both notes, and a note your pads never send is never heard.
- A hi-hat pedal pressed on its own is not in the preset, so a foot chick is ignored rather than counted as a stray hit. The same goes for any note outside the table: unknown notes are silent, never overhits.
- Alesis modules send the release of a pad as a zero-velocity note-on; WebEDrums treats that as a note-off, so releases never double as hits.
How do I keep the latency down?
The module's own sounds have no software delay. The lowest-latency setup is headphones or a speaker on the module with the song mixed in: a splitter or a small mixer joining the computer's headphone output and the module's output, or, on the Nitro Max, the computer's audio into the module's Aux input so that everything arrives on the module's phones jack. Alesis notes that headsets with a built-in microphone can be unreliable on that jack and asks for standard TRS headphones. The home page's sound setup diagrams show both wirings.
If you prefer the browser's drum sounds ("Kit sounds in the browser" in Settings, Audio, six kit styles), run the timing calibration once: eight clicks, hit the snare on each, about six seconds. It measures your computer's audio delay and judges hits against what you heard. Bluetooth audio from the computer into a Nitro Max adds its own delay to the song, so calibrate again after switching to it, or stay wired.
What works in Chrome and Edge?
Chrome and Edge on Windows, macOS, Linux and ChromeOS. The module appears under its USB name, the browser asks once for MIDI access (Chrome has prompted for all MIDI access since version 124), WebEDrums picks it as the drum input automatically, and the setting survives reloads. Firefox 108 and newer works after installing its site-permission add-on but cannot remember the songs folder between visits. Safari has no Web MIDI, so a Mac needs Chrome or Edge. YARG's hardware page lists the Nitro Mesh and Nitro Max as compatible kits, which is another way of saying their MIDI is entirely ordinary.
If the module is on but the browser lists nothing: check that the cable carries data, try another port without a hub (the Clone Hero wiki traces most such cases to USB power), and on Windows close any other program that has the module open.
Which games and apps read the Alesis Nitro?
Any of them that takes MIDI, since the module sends standard notes over USB. The setup differs per program: the Clone Hero drums setup and the YARG drums setup guides walk through the desktop games with the fixes for a kit that is not detected; the connection guide covers cables and drivers for all of them; and the comparison lays the apps side by side, WebEDrums included.
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.