Troubleshooting

When something sounds off

Search, or pick a category. Most grid problems are one click away.

The grid sits a little early or late against the kick

Beatdis adds a small nudge (default 3 ms) when writing, plus an automatic codec-delay correction for MP3s (about 23–25 ms; FLAC/WAV need none).

  • Grid ahead of the beat in your DJ software? Raise nudge a few ms and save again.
  • Whole grid shifted by a constant amount? Shift-drag any handle to slip the entire grid.
The BPM is half or double what it should be

Use the ÷2 or ×2 buttons in the toolbar to flip the octave. The grid re-fits instantly.

Beat 1 / the downbeat is on the wrong beat

Press phase −1 or +1 until the bar-start markers fall on the bar's first beat. Beatdis votes bar phase per section, so a track that re-phrases after a break is handled, but the global shift is yours to set.

A beatless intro or breakdown is throwing the grid off
  • Right-click → Analyze from here re-runs detection from that point.
  • Delete markers before / after here tidies intro and outro junk.
  • For a drifting breakdown, set an adjustment IN and OUT on two good markers, then Straighten region or drag an anchor to warp it onto the beat.
What do the red “bridged” bands and ⚠ labels meanNEW

Where the beat tracker finds nothing reliable (a drumless breakdown, a long riser), Beatdis scores candidate beat counts across the gap and picks the most plausible one. The band shows the length in beats and any phase shift.

⚠ uncertain means no count gave a plausible tempo — typically a real tempo change. Play it with the Click on, and fix it with an adjustment region if it's off.

Serato doesn't show the new grid

Serato caches grids by file, so an already-loaded track keeps its old one.

  • Re-import the track (or rescan the crate / “Re-load ID3 tags”).
  • If you wrote to a copy, load the new filename.
  • Check that Serato isn't set to re-analyse files on load — Beatdis sets BPM lock to prevent that.
Serato shows fewer markers than Beatdis

Serato caps a grid at 128 markers. Beatdis subsamples automatically when you save, so the grid shape is preserved. Use every 4 / 8 bars if you'd like a lighter grid.

An M4A won't analyse (“re-encode it”)

Some M4As are AAC Main profile, which the audio decoder doesn't support, so they can't be analysed or played. Re-encode to AAC-LC, MP3 or FLAC and try again.

Tagging itself still works, and files with an ID3 tag in front of the MP4 header are handled.

“Save to Rekordbox” says the track has no analysis

Beatdis edits the analysis Rekordbox already created, so the track must be imported and analysed in Rekordbox first. Add it, let Rekordbox analyse it, close Rekordbox, then save from Beatdis.

It won't write while Rekordbox is open

Rekordbox keeps its database locked while running. Quit Rekordbox completely (check the system tray), then save again. The new grid appears next time you open it.

Can I undo a Rekordbox write?

Yes. Before writing, Beatdis backs up master.db and each track's .DAT analysis file next to the originals as *.beatdis-bak. Close Rekordbox and copy a backup back over the original to restore.

Cues are missing or doubled in Rekordbox

Saving replaces the track's existing hot cues (A–H) with Beatdis's. To start from the ones already in Rekordbox, right-click the track → Load Rekordbox cues before saving, then edit from there.

“Models unavailable” or analysis won't start

Beatdis needs its beat and key models (~83 MB) the first time. Check your internet connection and press Analyze again — the download is retried and reused afterwards.

One file failed during a batch save

Batches never abort on a single bad file. The failing track is marked save failed (hover for the reason) and the rest carry on; a dialog lists everything that failed at the end. The failed track keeps its grid so you can fix the cause and save it again.

The playhead is out of step with the audio

Playback uses a native audio engine. If audio lags the playhead (seen most often on macOS), raise the sync value in the toolbar in 10 ms steps.

Windows warns when I launch the installer

Windows builds aren't code-signed yet, so SmartScreen shows a warning. Choose More info → Run anyway. The macOS build is signed and notarized.

No matches. Try a simpler word like “serato” or “tempo”.