Dead as Disco BPM Tracker Guide

How to read BPM without over-tuning

Use BPM as a clue, not a verdict. In a rhythm-action game, the useful question is whether the beat, input feel, audio device, and fight pressure line up when you actually play.

• A BPM number does not replace playing or watching the relevant section.
• Custom tracks and official songs should not be compared as the same kind of clip.
• If a number has no clear context, use it as a rough clue, not a setting to copy.

When a BPM number is worth using

Before you use a BPM number, ask what it is attached to. A number is more useful when it is tied to the exact song, clip, platform, audio setup, and a repeatable way to hear or measure it.

• Record the game version and platform with every value.
• Keep the clip or song name close to the number.
• Leave shaky numbers out instead of rounding a guess into certainty.

Offset And Rhythm Window Notes

BPM alone does not explain why a hit feels early or late. Separate the song tempo from input offset, audio delay, controller feel, and whether you are testing an official song or a My Music custom track.

• Do not treat custom-track behavior as official soundtrack behavior.
• Do not publish exact timing windows until they are repeatably tested.
• Keep audio hardware notes separate from game mechanics notes.

What to write down after testing

After a test, write down the song or clip name, the setting you changed, what felt better or worse, the game version, platform, audio setup, and whether it was My Music or an official track. Leave unknown numbers blank.

How to use timing clips

Timing clips are best for spotting what to check next: obvious beat drift, late hits, early dodges, or a custom track that feels different from the official songs. Watch for the problem, then test one setting at a time.

Mark outdated tutorials before copying settings

The July 3 intake added current import tutorials, Steam Deck custom-music setup, and at least one video that labels itself outdated. That means a good BPM note now needs a tutorial-age column. Record whether a clip shows the current UI, whether it still helps conceptually, and whether it predates the official Road Ahead plan for manual BPM detection in the next major update.

• Add a tutorial-age note before you keep any BPM or offset hint.
• Separate current UI, concept-only, and waiting-for-recheck clips.
• If a tutorial promises perfect line-up, treat that as a claim to test, not a value to copy.

Use Today's Clip Pool By Job

The current video pool is broad enough for timing work, but not every clip answers the same BPM question. Sort each clip by job before using it: official song feel, My Music import flow, calibration behavior, handheld setup, or high-skill score context. That keeps one attractive run from becoming a fake universal setting.

• Song feel clips help you decide what to test, not what value to publish.
• Import clips belong next to My Music notes before BPM notes.
• Handheld clips need device and build context before you compare timing feel.

Track Tempo Changes Separately From Offset

Recent custom-song tool discussions report that a value can feel correct for an early section and drift later when the source track changes tempo. That does not prove a universal editor rule, but it does show why one BPM and one offset field are not enough for every test. Add a section clip notes and a drift note before changing the global value.

• Test the opening, middle, and late section with the same device and build.
• Write where drift begins instead of immediately replacing the starting offset.
• Mark auto-detected values as tool output until a repeated play test confirms them.