How accurate is MixSleuth?
We checked every track.
We ran 12 DJ mixes (236 tracks, about 13 hours) through MixSleuth and through setlist.id, a popular online track-ID service, and checked every row against the DJ's own record of what was played.
A word on setlist.id first. We paid for every setlist.id scan in this test ourselves, at the normal price, and we think it's an awesome service: paste a link and a few minutes later you have a tracklist. It's the tool we set out to match, and it's the one to beat. This page is about where each one fits, not a takedown.
A tie: both found 95% of the tracks.
Rows naming a track that wasn't played. Fewer means less to correct by hand.
Matching against the DJ's own files, on 10 of the mixes. Free on every plan.
By genre
| Genre | Mixes | Tracks | MixSleuth found · wrong | setlist.id found · wrong |
|---|---|---|---|---|
| Drum & bass | 4 | 96 | 94 · 1 | 95 · 3 |
| Progressive | 4 | 74 | 72 · 3 | 72 · 7 |
| Melodic house & techno | 1 | 24 | 24 · 0 | 22 · 3 |
| House | 1 | 22 | 17 · 2 | 19 · 4 |
| 2000s trance | 2 | 20 | 17 · 4 | 17 · 14 |
| All | 12 | 236 | 224 · 10 | 225 · 31 |
- Drum & bass: near-perfect for both.
- Progressive and house: setlist.id found a few more tracks on two mixes; MixSleuth showed fewer wrong tracks.
- Melodic and 2000s trance: MixSleuth showed fewer wrong tracks.
Every mix
Press ▶ to listen on Mixcloud and check for yourself.
| Mix | Genre | Length | Tracks | MixSleuth | setlist.id |
|---|---|---|---|---|---|
| DNB Sessions · Dec '25 | Drum & bass | 59 min | 25 | 25 · 0 | 25 · 1 |
| DNB Sessions · May '26 pt 1 | Drum & bass | 55 min | 26 | 25 · 0 | 26 · 0 |
| DNB Sessions · May '26 pt 2 (Vocal) | Drum & bass | 68 min | 26 | 26 · 0 | 26 · 0 |
| DNB Sessions · May '26 pt 3 (Lighter) | Liquid DnB | 54 min | 19 | 18 · 1 | 18 · 2 |
| Progressive Sessions · Dec '25 Vol 1 | Progressive | 55 min | 17 | 17 · 1 | 15 · 0 |
| Progressive Sessions · Dec '25 Vol 3 | Progressive | 56 min | 19 | 19 · 0 | 19 · 1 |
| Progressive Sessions · Nov '25 pt 3 | Progressive | 69 min | 22 | 20 · 2 | 22 · 3 |
| Progressive Sessions · Best of 2H25 | Progressive | 78 min | 16 | 16 · 0 | 16 · 3 |
| Melodic Sessions · June '26 | Melodic house & techno | 83 min | 24 | 24 · 0 | 22 · 3 |
| Bonus House · 19 Nov | House | 55 min | 22 | 17 · 2 | 19 · 4 |
| 00s Trance Specials · pt 1 | 2000s trance | 73 min | 10 | 9 · 2 | 9 · 9 |
| 00s Trance Specials · pt 2 | 2000s trance | 74 min | 10 | 8 · 2 | 8 · 5 |
Each cell is found · wrong. MixSleuth figures are the 11 October run; hover a cell for all three nights.
Same answer every night
Online identification can vary from day to day, so we scanned all 12 mixes on three nights with the same audio and the same app.
| Run | Found | Wrong |
|---|---|---|
| Fri 9 Oct | 224/236 | 10 |
| Sat 10 Oct | 225/236 | 11 |
| Sun 11 Oct | 224/236 | 10 |
Speed and price
- Speed: about the same. setlist.id took about 6 minutes per hour of mix; MixSleuth about 7 on a Mac mini.
- setlist.id: $1.00–1.20 per hour of mix, with refunds for stretches it can't identify.
- MixSleuth Pro ($4.99/yr): one Standard scan a month (a mix up to 60 minutes) included. Beyond that, pay as you go with credits at $0.75–$0.99 per hour of mix, charged in proportion: a 90-minute mix uses 1.5 credits.
- MixSleuth Studio ($29.99/yr): unlimited Standard scans, no credits needed.
Pick MixSleuth if…
- you're tracklisting your own recorded sets, especially before you upload them
- you have the tracks in your own library: near-perfect, and free
- you want fewer wrong tracks to fix, and tools to fix the rest (rename, split, join)
- you want store links for every track (Apple Music, Spotify, Beatport and more), ready to buy what you heard
- you scan regularly and would rather pay a flat yearly price
Pick setlist.id if…
- you have a link to someone else's mix and just want the names
- you're not on a Mac, or don't want to install anything
- you want label and genre details for every track
- you only identify a few hours of mixes a year
How we tested
Whose mixes are these?
They're the developer's own DJ sets, published on Mixcloud as FalconD. That's deliberate: for your own sets you know exactly what you played, so every result can be checked against the real answer. It also means the genres lean towards drum & bass and progressive, and we'd love to repeat this with other DJs' sets.
What counts as “found” and “wrong”?
The answer key is the DJ's own play history exported from Rekordbox, so it lists exactly what was played. A row counts as found when its artist and title match a track that was played. A row is wrong when it names a track that wasn't played at all. A second row for a track that was already found counts as neither. Remix and version names aren't checked. Both tools were scored by the same script.
Which MixSleuth settings were used?
A Standard online scan with the default settings in MixSleuth 1.4.12 (including the default Light setting for short guesses): no Deep credits, and no matching against a music library. That's the scan included with Pro (one a month) and Studio (unlimited). Each tool got the same audio, downloaded from the mixes' Mixcloud pages.
Why were MixSleuth's scans run three times and setlist.id's only once?
Online identification gives slightly different answers from day to day, so we ran MixSleuth on three nights to show how much it moves: very little (224–225 found, 10–11 wrong). setlist.id is a paid service (we paid for it like any customer) and we ran it once, on 6 October 2026. Its results may vary in the same way.
What if I have the tracks in my own library?
Then MixSleuth can match the mix against your own files, which is free on every plan. On 10 of these mixes that found 215 of 216 tracks with 6 wrong rows. Online services can't do this, because they don't have your files.
Try it on your own sets
Free to try, runs on your Mac, and your files stay on your Mac.
30-day free trial · no credit card · macOS 13+ · Apple Silicon