Fixing input and audio latency in rhythm games

Lag in a rhythm game usually comes from three places stacked on top of each other: your display, your audio path, and the game’s own offset settings. Fix them in that order and calibration becomes easy instead of a guessing game. Here is where each delay hides, with numbers you can compare against your own setup, and how to cut it down.

Start with your display

Your screen can quietly add a chunk of delay before a single note ever reaches your eyes. TVs are the worst offenders because their picture processing (motion smoothing, noise reduction, dynamic contrast) buffers frames to look nicer, and every buffered frame is time you do not have in a rhythm game.

Try this, then adjust:

• Turn on Game Mode in your TV or monitor settings. It bypasses most of the heavy processing and is the single biggest win for TV players.
• Disable extras like motion smoothing, sharpening, and any “cinema” or “vivid” preset that layers on processing.
• If you are shopping, a low-lag gaming monitor generally responds faster than a typical living-room TV. You do not need the fanciest panel, just one built for low input lag.

You will not see an exact millisecond figure, and that is fine. The goal is to remove processing, then let calibration handle whatever delay remains.

Where refresh rate fits in

Refresh rate is how often the screen redraws, measured in hertz. The faster it redraws, the less time a frame sits waiting to be drawn. A 60 Hz panel finishes a new frame roughly every 16.7 milliseconds, 120 Hz every 8.3 milliseconds, and 240 Hz every 4.2 milliseconds. That matters in rhythm games because the chart you read is made of those frames, and stale frames mean stale timing cues.

Refresh rate is not the same as input lag, but they travel together on gaming monitors. A panel built for 120 Hz or 144 Hz play almost always also has low input lag in Game Mode. A high refresh rate does not rescue a TV loaded with picture processing, so turn Game Mode on first, then enjoy the higher rate.

Clean up your audio path

Timing in a rhythm game is mostly about hearing the beat, so audio latency matters as much as video. The general rule holds across setups, with rough numbers attached so you can see why wired usually wins:

Audio path	Typical added latency	Notes
Wired 3.5mm or USB headphones	Under 10 ms	Consistent; the safe default
2.4 GHz wireless dongle	Around 5 to 20 ms	Faster and more stable than Bluetooth
Standard Bluetooth (SBC codec)	Often 150 to 250 ms	Sounds fine for music, wrecks timing
aptX Low Latency or LC3	Roughly 30 to 50 ms	Better, needs matching support on both ends
LDAC and aptX Adaptive	Varies, sometimes 100 ms or more	Prioritizes sound quality over delay
PC default audio path	Varies widely	Low-latency modes and exclusive mode help

Wired almost always beats Bluetooth. Bluetooth compresses and buffers audio to travel over the air, and that adds latency you cannot fully calibrate away because it can drift. If you play seriously, plug in.

The reason codec choice matters is that standard SBC, the baseline Bluetooth codec, buffers audio in chunks to keep playback stable. Low-latency codecs like aptX Low Latency or the newer LC3 shrink those chunks, but only if both your headphones and your source device support the same codec, and many phones do not expose the option. A 2.4 GHz USB dongle sidesteps Bluetooth entirely and is the closest wireless option to a wired cable.

On PC, look for low-latency audio options. Some games let you pick an audio driver or exclusive/low-latency mode, and choosing the leaner path can shave off delay before you ever touch the offset. WASAPI exclusive mode on Windows is one common option. Console players have fewer knobs here, so the wired-versus-wireless choice carries most of the weight.

Calibrate the game’s offset

Almost every rhythm game gives you an audio offset, and many add a separate visual offset. The audio offset lines your button presses up with what you hear; the visual offset lines the on-screen notes up with the beat. When your hits feel consistently early or late even though your rhythm is good, the offset is the fix, not your hands.

A simple routine that works:

1. Calibrate in your real setup. Use the same screen, the same headphones, and the same controller you will actually play on. Change any of those later and you may need to recalibrate.
2. Go quiet and undistracted. A calm room helps you feel the beat instead of fighting background noise.
3. Run the built-in calibration if the game has one. Tap along to the metronome or test track and let it estimate your offset.
4. Adjust a little at a time. Nudge the offset in small steps, play a familiar chart, and feel whether hits drift earlier or later. Big jumps overshoot.
5. Trust your ears over the numbers. If it feels locked to the beat, it is calibrated, whatever the value says. Two players on identical gear can land on different offsets.

Where the offset setting lives in common games

Game	Setting name	What it does
osu! (stable and lazer)	Universal offset and per-map offset	Shifts every chart’s audio by a fixed amount; per-map offset handles one odd beatmap
Beat Saber	Note jump movement speed and note offset	Changes when notes reach you and where the swing line sits
Project Sekai / Project DIVA	Note speed and judgement timing	Speed sets arrival rate; judgement timing is the offset
Muse Dash	Note speed and offset	Speed for arrival, offset to slide timing earlier or later
A Dance of Fire and Ice (ADOFAI)	Visual offset and audio offset	Set separately so hit flashes line up with the music
Phigros	Note speed and offset	Speed sets how fast notes fall; offset slides timing

If hits feel off in a way tweaking audio offset cannot solve, check the visual offset separately. Audio-late and video-early feel different once you learn to tell them apart.

A camera trick to measure your chain

If you want to see your own latency instead of trusting specs, point a phone camera at your screen and your hands in slow-motion mode (most phones shoot 240 frames per second or faster). Tap a note and count the frames between your finger moving and the on-screen hit flashing. At 240 fps each frame is about 4.2 milliseconds, so a 5-frame gap is roughly 21 ms. Do the same with audio: record the click of your key and the game’s hit sound, then look at the gap on the waveform in any free audio editor. Numbers from your own setup beat any marketing claim.

Wireless controllers and VR

Wireless controllers add their own small input delay compared to wired. It is usually minor, often just a few milliseconds, but for tight charts a wired controller removes one more variable. If you are chasing your best scores, wire the controller too.

VR rhythm games layer in extra timing considerations from headset tracking, frame reprojection, and rendering. Most VR headsets reproject frames to hold the frame rate steady, and that step can quietly add a few milliseconds of its own. Lean on the title’s own calibration tools, set your headset to the highest stable refresh rate (72, 90, or 120 Hz on most consumer headsets), and recalibrate whenever you change headphones or audio output.

Quick checklist

• Display: Game Mode on, picture processing off, prefer a higher refresh rate when you can.
• Audio: wired over Bluetooth; enable low-latency or exclusive mode on PC.
• Controller: wired removes a small wireless delay.
• Offset: calibrate in your real setup, quiet room, using the same gear every time.
• Adjust the offset in small steps and trust your ears.
• Set visual offset separately if notes and beat still disagree.
• Recalibrate whenever you swap screen, audio, or controller.

Dial these in once and your inputs will finally land where you expect. From there it is just practice. For deeper drill on what good timing looks like across the genre, the reading charts and building accuracy walkthrough covers the rest of the craft, and the terms glossary spells out offset, judge, BPM, and the rest of the vocabulary the genre leans on.