You are halfway through a mix. The tempos match, the levels match — you bring up the next track… and it sounds like one long wrong note that refuses to go away. Two songs that were perfect on their own suddenly start fighting over the same notes.
That feeling is called key clash, and it has nothing to do with volume or speed. It happens because every song lives at a musical address — its key — and you just moved two strangers from different streets into one house.
The good news: in ten minutes you can learn a map that removes almost all of these clashes. Picking the next song by key — harmonic mixing — is an old DJ trick; the Camelot wheel is its modern shortcut, a clock face where every position carries a musical address, so "do these songs go together?" becomes simple arithmetic.
Why two songs can clash even at the same tempo
Every piece of music leans on notes from one family: its key. You cannot hear any single note in isolation and call it out, yet after ten seconds your brain knows "this is A minor" — exactly like recognizing a friend's voice in a crowd.
There are 24 families in total: twelve major and twelve minor. Major sounds bright and open; minor sounds darker and moodier. And here is the secret everything else runs on: many families share their DNA. C major and A minor use exactly the same twelve notes — only the emphasis differs. That is why some songs sit together like old friends, while others seem to argue from the first second.
The wheel exists so you never have to work that out in your head. It turns "do these two keys go together?" into a one-glance answer — no theory degree required.
The Camelot wheel: a clock face for your ears
Picture an ordinary wall clock with twelve numbers. Each number holds two addresses, stacked:
- the B ring (outer) — major keys, the bright ones
- the A ring (inner) — minor keys, the moody ones
So position 8 contains two twins: C major is 8B, and its relative key A minor is 8A. Same notes, different mood. Position 1 holds B major and A♭ minor; position 5 holds E♭ major and C minor — and so on around the circle.
One practical detail before you read any codes in the wild: spellings vary between sources (C♯ major and D♭ major are the same sound). The DJ convention — ours included — spells positions 1–4 with flats where applicable, so 3B is "D♭ major", never "C♯ major". The code itself, number plus letter, has no ambiguity.
And remember: a code says nothing about quality. A lo-fi bedroom beat and a festival anthem can both be 6A — same address, different furniture, identical neighbors on the wheel.
The full map of all twelve positions
Here is the complete wheel — exactly what our free BPM & key analyzer applies to whatever file you drop into it:
| Position | Major (B ring) | Minor (A ring) |
|---|---|---|
| 1 | B major | A♭ minor |
| 2 | F♯ major | E♭ minor |
| 3 | D♭ major | B♭ minor |
| 4 | A♭ major | F minor |
| 5 | E♭ major | C minor |
| 6 | B♭ major | G minor |
| 7 | F major | D minor |
| 8 | C major | A minor |
| 9 | G major | E minor |
| 10 | D major | B minor |
| 11 | A major | F♯ minor |
| 12 | E major | D♭ minor |
You do not need to memorize a single line. The whole point of the map is this: once you know where your current track lives, everything else is arithmetic — and if you just want an address without looking anything up, drop the file into the analyzer. It reads the key from the audio itself (it never trusts filenames or tags), prints the code, and circles the compatible neighbors on a drawn wheel.
Only three moves are actually safe
Knowing your current position gives you exactly two "safe" ways out — and one category of experiments:
1. Jump to your twin. 8A → 8B is A minor into C major: identical twelve notes, zero new pitches, nothing can clash. This is the safest move on the whole wheel — use it whenever you want a mood change with no risk at all.
2. Step one number left or right, staying in your ring. From 7A (D minor) you may go to 6A (G minor) or 8A (A minor). The numbers follow the ancient circle of fifths — each step is a fifth apart — which is why chords slide between neighbors almost without you noticing. Rule 1 plus rule 2 cover most of what professional transitions actually do.
3. Everything else is an experiment. Two or three steps can sometimes land well and add tension on purpose; more often than not, you will hear the friction that was never meant to be heard. Treat anything beyond ±1 as a choice your ears must approve — not a rule you fire blindly.
Worked example: your track is A minor (8A). The next song can safely be C major (8B) — its twin, zero new notes — then D minor (7A) and E minor (9A), one step either way on the A ring. That is four compatible options per position in any library, which almost never runs out before an ugly move would have been forced on you.
BPM: the second number people skip
The wheel answers "will the notes clash." Tempo decides whether a transition feels like one piece of music at all. A few rules from people who do this for a living:
- Keep your set inside one window. Every genre has its own 10–15 BPM neighborhood; jumping outside it resets the energy no matter how perfect the key match was.
- Match small deltas straight, plan bigger ones. Same tempo grid = seamless handover. Double/half-time relationships (62 ↔ 124) work — but that is a filter move, not a crossfade.
- Beware of the half-time trap when reading numbers. A half-time groove genuinely lands at both 70 and 140, so detectors report candidates rather than intentions. If the reported tempo sounds double (or half) of what you hear, trust your ears — our analyzer shows a confidence score and lists every candidate in its debug panel precisely for this case.
- Do not stretch too far. A few percent is transparent; push further and voices start sounding like they are underwater. Whatever file you prepare to ship — including AI-generated songs — the pre-release checklist in mastering Suno output covers what to look at first.
- If your work touches time-based effects, lock them to this same grid. Once a track's tempo is settled, any delay or reverb you add should sit on its musical divisions — the free BPM → delay & reverb time calculator converts that number into exact millisecond values (plus cycles and phase) so your FX lines up with the beat instead of drifting behind it.
The third thing: what a spectral balance shows you
This is where people trip up even after mastering key and tempo. Two tracks can agree on everything and still sound muddy when stacked, if both of them own the same frequency range — say, both play heavy bass between 32–100 Hz. Then two basslines sit on top of each other until the low end turns into a soup where neither is audible anymore.
The analyzer reports energy across seven bands — Sub, Bass, Low-mid, Mid, High-mid, Presence, Air — plus a spectrogram you can read by eye. What that is for: if both tracks are bass-heavy, plan for one of them to duck or filter out during the handover instead of a straight blend; and if the incoming track is simply louder (that is what LUFS measures — and why true peak still matters after streaming re-encodes: our true-peak explainer), it will dominate the transition no matter how compatible the keys are.
Key + tempo tell you whether a move is possible. Spectral overlap tells you what that move will cost in the mix. Read all three numbers before ordering a set, and most of the guesswork disappears.
Put it into practice (five minutes)
- Run both candidate tracks through the free analyzer. Decoding and detection happen entirely in your browser — nothing is uploaded anywhere, so unreleased material stays private.
- Read the two codes; pick a neighbor from its four safe positions.
- Check the BPM delta: small = straight handover; large = plan an energy move around it.
- Compare the bands: both bass-heavy? Put low-end movement into the transition instead of a pure crossfade.
- Write down your set's codes as you build it — five minutes of this before a gig or a mixdown session beats an hour of fixing clashes live.
One honest boundary: mastering does not move a track's key or tempo. What we do in full AI mastering is polish loudness, tone and dynamics so files land at streaming targets (what that adds over a raw export) — but the key/BPM work above stays yours: your ears plus this map.
Frequently Asked Questions
Does a "better" code mean a better song?
No. The code is only an address on the wheel — 6A is G minor whether that G minor is a lo-fi loop or a festival anthem. The compatibility rules apply equally to every genre; taste decides which compatible tracks actually sound good together beyond the math.
I love two tracks, but their keys do not match. Any way around it?
Three honest options: (1) find a bridge track — some third key that is compatible with both, so you chain two safe moves instead of one unsafe one; (2) accept the clash as an intentional stylistic moment — some genres live for exactly this; (3) shift one track by a semitone or two with pitch-shifting software. Small shifts are nearly transparent; large ones sound artificial. If you want to see how contested the reading was before deciding what to trust, the analyzer's debug view lists every key candidate with its score.
Why does the analyzer say major when I know my track is minor?
Usually because the relative-major/minor pair is genuinely ambiguous in recorded material — 8A and 8B are the same twelve notes with different emphasis, and a detector averages the whole file. If your DAW says A minor while the tool reports C major at similar confidence, you are looking at the same position on the wheel anyway (number 8), which mixes identically either way.
I am not a DJ — is any of this useful for producers?
Yes. Knowing a track's key helps when writing continuations (chords in compatible keys sit under existing material far more predictably), when arranging layers inside a DAW, and when deciding how two exported tracks should be used together in a release. The same four safe neighbors apply whether you are building a live set or sequencing a playlist — drop studio exports, stems, or AI-generated files into the free analyzer and read the code before committing to how they will sit together.