# Why does my rhythm game feel out of sync? Your audio is late > Your device plays sound a fixed moment late, so on-beat taps register late. How to tell, which way to move the offset, and how to calibrate it out. Source: https://apps.swtlm.com/blog/why-does-my-rhythm-game-feel-out-of-sync · TLM Apps — focused mobile apps from a team of engineers. Published: 2026-08-27 · Updated: 2026-08-27 · TLM Software Design Your rhythm game feels out of sync because your device plays every sound a fixed moment after the game asks for it. Wireless earbuds add enough of that delay that [Arrows Rhythm](https://apps.swtlm.com/arrows-puzzle-game) sizes its calibration slider at ±200 ms, against a Perfect window of ±53 ms on its default 90 BPM track. The delay is a constant for your device, not a fresh number each launch. That is what makes one calibration worth two minutes of your time. ## Is it your timing, or the game's? Output latency is the gap between a game calling for a sound and that sound reaching your ears. The game asks, the system mixes, the hardware converts, and only then does air move. How much time that takes differs by phone, by headphone, and by whether the path is wired. The game meanwhile scores your tap against its own beat grid. On that grid the beat happened the moment it asked for the sound. So you tap to a beat that, as far as the game is concerned, has already passed. Scale decides whether you notice. Arrows Rhythm counts a tap as Perfect within 8% of a beat either side. On the Steady track it starts you on, which runs at 90 BPM, that is ±53 ms. A delay that size is inaudible as delay and fatal as scoring. One check separates a device problem from a skill problem. Misses caused by latency are lopsided: nearly every verdict lands on the same side of the beat, run after run. Misses caused by timing scatter on both sides. ## Why is the delay the same on every launch? A game has two clocks it could anchor its beat grid to, and the choice decides whether calibration is worth anything. The easy one is a clock started when the app launched. Audible beat 0 does not land when the app starts, though. It lands whenever the platform actually gets the player going, a variable amount of parsing and setup later. Pausing makes it worse: the audio freezes and the clock does not, so every trip to the home screen shifts the phase again. The other option is to anchor the grid to the audio itself. Arrows Rhythm does this. The sound player reports the loop's playback position whenever it jumps — a fresh start, or a resume after the app came back to the foreground. The engine then slides the grid so beat 0 lines up with loop position 0. That only holds if loop position 0 really is beat 0, so the three tempo beds are generated as a whole number of bars and stored losslessly. Anchoring does not remove output latency, and is not meant to. It converts it from a random per-launch error into a constant per-device one. The whole idea of calibration rests on that: a slider cannot correct an error that re-randomises every launch. A lossy codec would undo the anchoring quietly. Its encoder padding shifts the loop point by a few milliseconds at every seam, and the shifts accumulate. So the beds are written as whole bars, with the tail fade switched off, and kept lossless. A grid that slips one seam at a time is one you calibrate at the start of a session and not at the end. ## How to calibrate in about two minutes Calibration is a measurement, so make the conditions match the way you play. 1. **Use the output you will actually play through.** The offset is one number describing one audio path. Calibrating on the speaker and playing on earbuds gets it wrong twice. 2. **Turn the music up enough to hear the beat clearly, and tap to the sound.** Not to the animation, and not to your own count. 3. **Play a short stretch and read the verdicts.** Consistently on one side means a device offset to remove. Mixed means calibration is not your problem. 4. **Move the offset, then check again.** Steps of about 20 ms are big enough to feel between runs; fine-tune once the direction is right. The direction is the part people get backwards. Hearing the beat late is the usual case on wireless. It means your tap is late on the game's grid, so the reading has to shift **earlier**, which is a negative offset. Firing ahead of the beat is the opposite and takes a positive one. In Arrows Rhythm the control is **Settings → Rhythm sync**. It is a slider running to ±200 ms, with a minus and a plus button either side that nudge it one millisecond at a time, and a Reset back to 0. The offset moves the tap classifier only. The beat wave on the board keeps following the audio, so calibrating your scoring does not desync your screen. ## Why do wireless earbuds make it worse? Because a wireless path does more work before your ear gets anything. The audio is compressed, transmitted, buffered at the other end and decoded. Each of those steps costs time a wired path does not spend. That is why the slider runs to ±200 ms rather than a few dozen: the range is sized for wireless audio, not for a phone speaker. Two things follow. Switching output device means calibrating again, because the number you saved describes the path you saved it on. And it is worth redoing after a headphone change even when nothing feels wrong: a smaller error still costs you Perfect verdicts you were earning before. Latency is also the word for the round trip a connection measures, which is [ping, jitter and packet loss](https://apps.swtlm.com/blog/what-ping-jitter-and-packet-loss-mean) — different numbers with different symptoms. Your wifi has nothing to do with this one. Arrows Rhythm's Regular levels run offline, so the beat grid and your taps are both on the device. ## What if calibrating does not fix it? Then it is one of these, and knowing which saves you fiddling with a slider that was never going to help. - **The number that worked yesterday is wrong today.** The game re-anchors its grid differently on each launch, and no saved offset survives that. There is nothing you can set, which is the honest answer. - **It starts fine and drifts within one session.** That is arithmetic in the game, not you. A beat at 90 BPM is 666.666… ms long, and a build that rounds it to 666 accumulates roughly a tenth of a per cent per beat until the visual and the audio disagree. - **You see the pulse and hear the sound at different moments.** On a delayed output path they genuinely arrive apart. Arrows Rhythm draws the wave from the track's own timeline and does not apply your offset to it. Follow the sound, and calibrate to it. - **You would rather not have a timing layer.** Fair. A master Rhythm switch in Settings removes the verdicts, the wave and the rhythm stats across every mode, and swaps the percussive bed for a calm ambient loop. Each successful tap in Regular and the Daily then pays a flat ArrowCoin rather than a per-verdict amount, so the earn loop survives the decision. A game can feel unfair for reasons decided in the build rather than at the moment you play. [Mahjong solitaire](https://apps.swtlm.com/blog/are-mahjong-solitaire-boards-always-solvable) has the same shape: a random deal can be unwinnable before you touch it, which is why [Midnight Mahjong](https://apps.swtlm.com/mahjong-solitaire) builds its default boards during a simulated playthrough instead of scattering the tiles first. Knowing which is which is most of the fix. [Arrows Rhythm](https://apps.swtlm.com/arrows-puzzle-game) keeps its sync slider in plain Settings rather than behind a calibration minigame. Levels 1–500 are free and the rest are a one-time $2.99. The only ads are a banner in Zen mode, the one mode with no rhythm layer, and a separate $1.99 purchase removes it. The reasoning behind saying all that out loud is in [what a puzzle game subscription costs](https://apps.swtlm.com/blog/what-a-puzzle-game-subscription-costs). If you would rather work on the thinking than the timing, [block puzzle strategy](https://apps.swtlm.com/blog/block-puzzle-strategy-keeping-the-board-open) is the one to read next, and the rest of the shelf is on the [Games page](https://apps.swtlm.com/games). ## Frequently asked questions **Why does my rhythm game feel out of sync?** Your device plays sound a fixed moment after the game asks for it, so the beat you hear has already passed on the game's clock. Tapping to what you hear therefore lands late. A calibration offset shifts how the game reads your tap so the two line up again. **Is the delay different every time I open the game?** It should not be. Output latency belongs to your device and your audio path, so it is the same on each launch — provided the game anchors its beat grid to the audio rather than to a clock started at launch. Arrows Rhythm anchors to the playback position the sound player reports, which is what lets one saved offset keep working. **Which way should I move the calibration offset?** If you hear the beat late, which is the usual case on wireless earbuds, your taps land late on the game's grid, so shift the reading earlier with a negative offset. If you tend to fire ahead of the beat, use a positive one. In Arrows Rhythm the control is Settings → Rhythm sync and it runs to ±200 ms. **Do I need to recalibrate when I switch headphones?** Yes. The offset is one number for one audio path, and a wireless path adds much more delay than a phone speaker. Switching output means setting it again, or resetting it to 0. **What if I do not want the timing layer at all?** Turn it off. Arrows Rhythm has a master Rhythm switch in Settings: off means no Perfect, Good or Off-beat verdicts and no beat wave, and each successful tap in Regular or the Daily pays a flat ArrowCoin instead. Its Zen mode ships without the rhythm layer in the first place.