The DJ set track identifier that finds what Shazam misses.
Shazam names one moment. ryser.id names the whole set: every segment, timestamped, with the tempo-warp and denoise rescue passes that catch the tricky ones.
Every segment, not one moment
Shazam listens to a few seconds. ryser.id segments the entire mix at the transitions and identifies each section end to end.
Catches the hard ones
Tempo-warped, pitched or layered tracks that a single fingerprint misses get tempo-warp and denoise retries plus a preview-verification pass.
Says when it's unsure
Unreleased and white-label tracks can't be fingerprinted; those stay marked unknown, with community suggestions to fill them in, instead of a wrong guess.
Drop the mix
A YouTube, SoundCloud or Mixcloud link, or an audio file up to 500 MB.
The cascade runs
Two independent fingerprint engines fire on every transition-cut segment; rescue passes retry what they miss, filling the setlist live.
Get the tracklist
Timestamps, BPM, Camelot key, cover art and streaming links, shareable and exportable.
Why is finding a DJ set's tracklist so hard?
A DJ set is deliberately engineered to hide its seams. Tracks are beat-matched, so two records play at the same tempo, which means at least one of them is pitched away from its release tempo, sometimes by 6–8%. Transitions overlap two tracks for 30–60 seconds, EQs carve out basslines, and hard-style sets layer acapellas and edits on top. Every one of those techniques is exactly what defeats one-shot fingerprinting: apps like Shazam match a clean 10-second sample against the original recording, and a pitched, layered, EQ'd section simply isn't the original recording anymore.
That's why the classic answers (scrolling comments for "ID?" threads, hoping a 1001Tracklists curator got there first, or Shazam-ing your phone at the speakers) are all partial. Comments cover the popular moments; curated databases cover the famous sets; live Shazam covers whatever happened to be playing clean when you tried.
ryser.id approaches it as a signal-processing problem instead. The mix is cut at its transitions, each segment is fingerprinted individually, and the sections that fail get rescue passes: the audio is tempo-warped back toward release speed, denoised, and cross-checked against candidate previews before a match is accepted. What can't be verified is labelled unknown, honestly, and community suggestions from YouTube and SoundCloud comments plus 1001Tracklists data fill in what fingerprinting fundamentally can't (unreleased and white-label tracks). The result is a timestamped setlist of the whole set, not a lucky sample of it.
How do I find the tracklist of a DJ set?
You have four options: scroll the comments hoping someone asked 'ID?', check 1001Tracklists in case a curator already documented the set, Shazam it moment by moment on your phone, or run the whole set through an automated identifier. ryser.id does the last one: paste the link, and it segments the mix at the transitions and identifies every section; a 60-minute set typically takes 6–10 minutes and comes back timestamped.
What's the best way to identify songs in a mix?
For a single moment, Shazam on your phone is fastest. For a whole mix, segment-by-segment analysis wins: continuous DJ mixes are beat-matched and often pitched several percent, which defeats one-off fingerprinting. An analyzer built for sets compensates for tempo shifts and retries hard sections with cleaned-up audio.
How is this different from Shazam?
Shazam identifies a single ~10-second sample. A DJ set is a continuous, often beat-matched and pitched mix; ryser.id segments the whole set and identifies every section, then applies tempo-warp and denoise rescue passes to the tracks a lone Shazam can't catch.
What sources can it identify?
Any YouTube, SoundCloud or Mixcloud link, or an uploaded audio file (MP3, WAV, FLAC, M4A and more) up to 500 MB.
Will it find unreleased or white-label tracks?
Fingerprinting can only match released music, so true unreleased/white-label IDs stay marked unknown rather than guessed. The community suggestion flow lets other listeners crowd-ID those.
How accurate is it?
It identifies most commercially released tracks in a typical set. Accuracy depends on the mix: heavy layering, edits and unreleased material are the hard cases the rescue passes and community IDs are there to help with.
How long does an analysis take?
Roughly a tenth of the set length: a 60-minute mix is usually done in 6–10 minutes. Results stream in live while it runs, and you get an email when the setlist is ready.
Can I identify tracks from a YouTube DJ set?
Yes: paste any YouTube, SoundCloud or Mixcloud URL. Playback afterwards streams from the original platform, synced to your timestamped setlist, so nothing is re-hosted.
Know every track in the mix.
120 free credits on sign-up. No credit card.