Tempo, key & filenames
BackTrackR fills Title, Artist, Tempo (BPM) and Key from your file and folder names at import. The song title comes from the folder name. A date at the start of a file name does not become the title. If tempo or key is still missing, the app can detect them from the audio in the background — detect only fills empty fields; it does not overwrite values already set by the name or by you in Edit.
Where values come from
- Filename / folder name — parsed at import (fastest, most reliable when you know the values)
- Song manifest — values already stored with the song
- Automatic detect — listens to the WAV stems when BPM or key is still empty
- You typed it in Edit — your values are kept; background detect will not overwrite them
Best practice: Name files with tempo and key when you know them. Use detect only as a fallback for songs that arrive without that information.
Name files for best results
Separate parts with space-hyphen-space ( - ). Underscores in names are treated like spaces. Tempo and key can appear in any order; the remaining text becomes Title, then Artist. On multi-stem songs, the part that differs per file is the instrument/track name.
My Song - Band Name - 120bpm - Am - BAS.wav120bpm - My Song - Am - Band Name - GUITAR.wav(same metadata — order of BPM/key does not matter)My Song - Band Name - 128bpm.wav(single file)- Folder name fallback:
My Song - Band Name - 120bpm - Embedded in free text:
drum_loop_120bpm,sang titel (Am, 103BPM)
Tempo forms: 120, 120bpm, 120 BPM, bpm120 (range 20–300). Key forms: Am, C#m, Bb, Fmaj, G minor, or a root in brackets like (C).
Automatic detect (when names are incomplete)
After import, if BPM and/or key are still unknown, BackTrackR queues background analysis — one song at a time while the app is idle. You can keep browsing the library.
In the library BPM and Key columns:
- Number / key (e.g.
120,Am) — value known - Spinner — detect is running or queued
- ? — detect finished but could not decide confidently (or key was skipped — no suitable harmonic stem). Enter the value yourself, or run detect again.
- — — still unknown; detect not finished or not queued yet
Stop playback first: Tempo/key detection does not run while a song is playing. If detect was mid-analysis when you press Play, it pauses and restarts that song from scratch after you stop — so a half-finished guess is never saved.
Re-run detect
- Library: long-press the BPM or Key column, then release (status shows “Release to detect…”). Runs that field only.
- Edit Edit
(pencil on the show screen): open the song → tap Detect tempo and/or Detect key.
Show, hide, or reorder the BPM and Key columns under Settings → General → Song list metadata — that only changes what you see, not whether detect runs. See Song list metadata.
Why you might see “?”
- Stems are very quiet, sparse, or not rhythmic
- No clear tonal centre (noise, speech, effects-only)
- Conflicting stems — the app refuses a low-confidence guess rather than inventing a wrong BPM
- Key skipped: only percussion / click / timecode stems — nothing tonal enough to analyse
What BPM is used for
- Timeline → Bars and musical Snap — need a stored song BPM (name, detect, or typed). An empty field that only looks like 120 does not count.
- Pitch & tempo — uses the song’s stored BPM when present
See also Navigate the arrangement and Pitch & tempo.