Electronic drum latency is the delay between striking a pad and hearing the sound. Before changing a buffer, driver or trigger setting, find out whether the delay exists in the drum module itself, the monitoring path, or the computer/VST path. The fastest test is to listen directly from the module, then add one device at a time.
Latency checklist
- Test wired headphones directly from the module before changing software.
- Add one device at a time to locate the stage that introduces delay.
- A smaller buffer can reduce latency but may cause clicks or dropouts.
- Use one monitoring path to rule out an echo caused by double monitoring.
- Record the driver, buffer, sample rate and signal path for each test.
Start with a direct-module test
- Disconnect the computer, phone, Bluetooth speaker and TV.
- Plug wired headphones directly into the drum module.
- Select a built-in kit and strike the snare and hi-hat with normal playing force.
- Repeat with a second wired pair of headphones if the response still feels delayed.
If the built-in sound feels immediate, the pads and module are probably not the main source of the delay. Reconnect the next device in your usual path and test again. If the delay is already present through the module’s headphone output, consult the model manual or manufacturer support before changing computer settings; a DAW buffer cannot fix a delay that occurs before the computer.
Write down the signal path you are actually hearing
Two setups can look similar but have different round trips:
- Module monitoring: pad → module sound → wired headphones or monitor.
- Computer instrument: pad → module MIDI/USB → computer → drum software → audio driver/interface → headphones.
- Recorded module audio: pad → module audio → interface/computer → DAW monitoring → output.
- Wireless playback: any of the above → Bluetooth or network audio device.
The computer paths add processing stages. Ableton’s latency documentation explains that conversion, audio buffers, drivers and plug-ins can all contribute to latency. Its latency-reduction guide also recommends avoiding Bluetooth or Wi-Fi audio for real-time monitoring, so use wired headphones or monitors while diagnosing.
Use an A/B isolation sequence
| Test | Listen through | If this is delayed |
|---|---|---|
| A | Wired headphones from the drum module | Check module/model support, trigger behavior and output routing |
| B | Same module audio through a wired amp or monitor | Check the cable and whether the speaker adds digital processing |
| C | Computer/VST through the computer’s selected output | Check the audio driver, buffer, plug-ins and CPU load |
| D | Computer/VST through a dedicated audio interface | Check the interface driver, buffer and monitoring route |
Change only one connection between tests. Otherwise, an improvement will not tell you which stage caused it.
If the computer or VST path is late
Open the DAW or drum software’s audio settings and confirm that the intended output device and its manufacturer-supported driver are selected. A larger audio buffer gives the computer more time to process audio but increases delay; a smaller buffer reduces delay but makes clicks, dropouts or distortion more likely when the system cannot keep up. This tradeoff is documented by both Ableton and PreSonus.
- Save the current setting so you can restore it.
- Disable high-latency plug-ins on the monitored path, especially look-ahead processing or heavy effect chains.
- Lower the buffer one step and play a repeated hi-hat pattern.
- Stop when response feels usable or when clicks/dropouts begin.
- If artifacts begin first, return to the last stable buffer and reduce CPU load or use a supported dedicated interface/driver.
Do not copy a sample-rate or buffer number from another setup as a guaranteed answer. The lowest stable setting depends on the computer, driver, interface, project and plug-ins. Record the buffer, sample rate, driver and round-trip latency reported by the software so you can compare changes.
Separate double monitoring from true latency
An echo-like second hit can occur when you hear the module’s direct sound and a delayed software sound at the same time. Mute one monitoring path. If the “echo” disappears but the remaining sound is responsive, the problem was duplicate monitoring rather than unusually slow pad triggering.
Choose one sound source while playing: either monitor the module directly or monitor the virtual instrument through the computer. When recording MIDI to use a VST, turn down or mute the module’s local sound if it creates a distracting second attack.
Match the symptom to the next change
| Symptom | More likely cause | Next check |
|---|---|---|
| Module headphones feel fine; Bluetooth is late | Wireless playback path | Switch to wired headphones or monitors |
| VST is late but built-in module sound is fine | Driver, buffer, interface or plug-in path | Select the supported driver; test a smaller stable buffer and an empty project |
| Two attacks or an echo | Direct and software monitoring together | Mute one monitoring path |
| Small buffer reduces delay but causes clicks | System cannot process that setting reliably | Return one step, remove heavy plug-ins, close background load |
| Only one pad feels late or inconsistent | Trigger/cable/pad issue rather than system-wide audio latency | Swap inputs or cables if the manual permits; check trigger settings for that pad |
Keep a short test record
For each test, note the connection path, output device, wired or wireless monitoring, driver, sample rate, buffer, active plug-ins and result. This prevents cycling through the same settings and gives support enough context to reproduce the problem. If you contact The ONE about a specific model, include the module name, firmware/app version if visible, computer and operating system, connection type and whether direct module monitoring is delayed.
Frequently asked questions
Does Bluetooth cause electronic drum latency?
Bluetooth audio can add noticeable delay to a live monitoring path. Use a wired connection when testing or performing.
Do you always need an audio interface?
No. If you use the module’s built-in sounds and wired headphone output, an interface may not be part of the path. A supported interface and driver can help a computer/VST setup, but it does not fix every source of delay.
Is the smallest buffer always best?
No. Choose the smallest setting that remains stable in the actual project. If clicks or dropouts begin, return to the last stable setting and reduce processing load.
Why do you hear two drum attacks?
You may be hearing the module directly and the computer-monitored sound a moment later. Mute one path before diagnosing additional latency.
