Imported a song, but the beats do not line up?

Try this worked example with a steady 120 BPM recording you have permission to use. The numbers below illustrate timing; they are not a measured result for your track or hardware.

Check the game's own detection first if your build offers it. The developer's September 29, 2026 update announcement reports automatic BPM and offset detection in Infinite Disco. This manual example helps when the resulting alignment still needs checking.

  1. Start with 120 BPM, Normal timing and a 0 ms offset. One beat is 500 ms; four beats take 2 seconds. Check an early section and a later section of the same recording.
  2. If the gap grows, re-check the tempo or tempo changes first. A fixed offset cannot fix drift. If the gap stays constant, keep the BPM fixed and compare 0 ms with one small offset adjustment.
  3. This example records +20 ms as a trial note. Test it in the game: keep the direction only if alignment improves; return to 0 and try the other direction if it gets worse. Follow the labels in your installed game version.
  4. Compare half-time and double-time: 120 BPM becomes 60 BPM / 1000 ms or 240 BPM / 250 ms. Offset changes the alignment note, not these intervals.
  5. After checking the same early and late sections in game, save your checked note in the calculator. Restore it on this device next time, or copy the result and its settings link.

Load the 120 BPM / +20 ms example

The browser calculator does not listen to audio, measure latency, or change game settings. Saving a note records your own manual check, not an automatic sync guarantee.

Problem Diagnosis

Identify your sync issue by matching symptoms with likely causes and recommended fixes.

Symptom Likely Cause Fix
Beats arrive consistently early (visual before audio) Audio offset is too low Increase audio offset by 10-20ms increments
Beats arrive consistently late (audio before visual) Audio offset is too high Decrease audio offset by 10-20ms increments
Sync starts fine but drifts over time Incorrect BPM value Look up the BPM in a track listing or measure it with a separate tap-tempo tool, then use the BPM Calculator for beat timings
All songs are universally out of sync System-wide audio latency Check Bluetooth/audio driver settings; use wired headphones
Audio stutters or crackles during gameplay Buffer underrun or CPU bottleneck Close background apps; increase audio buffer size
Only one specific song is out of sync Corrupt BPM metadata or VBR encoding Re-import with manually set BPM; re-encode as CBR MP3

Sync Fix Checklist

Work through this checklist to resolve BPM sync and audio delay issues.

What a one-BPM error actually costs

Why "close enough" is not a useful standard in a beat-synced game.

A BPM value errors in one direction: the gap it produces grows with every beat. At 128 BPM one beat lasts 468.75 ms; enter 127 BPM instead and one beat lasts 472.44 ms. The difference is 3.7 ms per beat, which is invisible on the first bar and about 236 ms after 64 beats — roughly half a beat at that tempo, and well past the point where an input reads as late. Thirty seconds of music is enough to expose it.

An offset error behaves the opposite way. It is constant: the whole grid shifts once, and the shift is identical at the first bar and the last. That is why changing the offset can never fix a growing gap, and why changing the BPM to fix a constant gap only moves the problem to the other end of the song.

This is also the reason the order of operations matters. Check the tempo first with a measured span or a second source, then set the offset, then look at the audio chain. Doing it in the other order means you are compensating for an unknown error with a second unknown error, and the settings you end up with describe your session rather than the song.

One more practical consequence: a calibration that holds for a four-minute track can still fail on a longer playlist. If the tempo is off by a fraction of a BPM, each successive track starts from a slightly different grid, and after five tracks the difference is audible again. Fix the tempo per track rather than averaging the error across a set.

Sync Methods and Tools

Three essential approaches for achieving perfect beat synchronization.

BPM Detection

The most common cause of sync drift is an incorrect BPM value. Even professional tracks occasionally have BPM metadata errors. Always verify BPM manually.

  • Use a separate tap-tempo tool (the BPM Calculator has no tap control)
  • Check online BPM databases for commercial tracks
  • Calculate from track duration and beat count
  • Re-verify after any speed or pitch changes

Offset Fine-Tuning

Audio offset compensates for hardware latency and encoding delays. Small adjustments can make a dramatic difference in gameplay feel.

  • Adjust in 5-10ms increments for precision
  • Positive offset: delays visual beats
  • Negative offset: advances visual beats
  • Use the Song Sync tool for calibration

Audio Device Optimization

Your audio hardware and software settings can introduce significant latency. Optimizing your setup eliminates many sync issues.

  • Always use wired audio for rhythm games
  • Disable audio enhancements and spatial audio
  • Set sample rate to 44100 Hz or 48000 Hz
  • Update audio drivers to latest version

Measure a span before you change a setting

Note the time of the first hit and the last hit in a section, count the beats between them, and enter all three values. The result shows the tempo your span implies. One span cannot separate an offset from a tempo error, so compare an early section with a late one before deciding. 中文版

If the tempo itself is in doubt, measure it again with the tap tempo tool; if the tempo is right and the gap is constant, the offset calculator explains the direction of the change.

Frequently Asked Questions

Quick answers to the most common BPM sync and audio delay problems.

BPM drift occurs when the BPM value set for your song is slightly inaccurate. A difference of even 0.5 BPM will cause noticeable desync after 30-60 seconds of gameplay. Measure the tempo with a separate tap-tempo tool for at least 15-30 seconds to get a precise reading, then enter it in the BPM Calculator to see the resulting beat timings. Re-import the song with the corrected BPM value. Also check that the song was encoded at a constant bitrate (CBR) rather than variable bitrate (VBR), as VBR files can cause timing inconsistencies.

System-wide audio delay is almost always caused by Bluetooth audio. Bluetooth introduces 100-300ms of latency that cannot be fully compensated. Switch to wired headphones or speakers for Dead as Disco. If you must use Bluetooth, look for low-latency codecs like aptX Low Latency, but even these are inferior to a wired connection for rhythm games. Also check that no audio enhancement software (Dolby, DTS, spatial audio) is active, as these add processing delay.

A correctly set offset means the beat markers on screen hit their target zone exactly when the beat occurs in the music. To verify: start a song and watch the beat markers. If they cross the target line before you hear the beat, decrease your offset. If you hear the beat before the markers reach the target, increase your offset. Use our Offset Calculator for a precise starting value, then fine-tune by feel during gameplay.

Sources for the game facts on this page

Checked November 14, 2026. Manual tempo entry, the planned automatic detection, and the My Music workflow come from the developer's Early Access notes and Midsummer update announcement; the Steam store page describes My Music. The drift arithmetic is ours and can be reproduced with the tool above.