Make the evidence visible
TuneReveal.com is a collection of music theory analysis tools for listeners who prefer an understandable working process to a mysterious answer. Bring a BPM you measured, a key you suspect, a meter you counted, or a frequency you observed. The tools organize those inputs, perform clearly described calculations, and help you compare musical relationships. They do not listen to a recording, open a video link, fetch a catalog result, or pronounce a song solved.
That boundary is the point. A key label can depend on which passage you examine. A tempo can be counted at double or half the pulse another listener chooses. A meter describes how beats are grouped, not merely how fast they arrive. When those judgments stay visible, you can revise them as your listening improves instead of treating a machine-generated label as permanent.
Start with the workbench
The song analysis workbench is the best first stop when you already have several observations. Enter a short private label, known BPM, observed key, meter, confidence level, and optional notes. The browser assembles a structured observation card and calculates useful timing values such as milliseconds per beat and seconds per bar. If a conventional key is supplied, it can also show related-key references. Your entries remain in the current page session and are cleared when you reset or leave; there is no upload or account.
Use the smaller tools when one question needs attention:
- Look up the accidentals associated with a conventional major or natural-minor key.
- Transpose recognized note names and chord roots by a chosen chromatic interval.
- Map a major or minor key to its commonly used Camelot code.
- compare two entered keys against a visible set of harmonic-mixing rules.
- convert a measured frequency to the nearest equal-tempered note.
- derive BPM from a counted number of bars and an elapsed time.
Each result includes its assumptions. That makes the calculation something you can audit rather than a label you must trust.
A practical listening example
Imagine that you are preparing notes for a four-bar loop. You tap or count the pulse elsewhere and settle on 96 BPM. The loop sounds centered on A minor, appears to group four quarter-note beats per bar, and ends on an A minor chord, but one bright F-sharp passing tone leaves you less than certain. In the workbench you enter 96, A minor, 4/4, and medium confidence. You add the note: “A feels stable at the end; F-sharp occurs briefly in the melody.”
The result reports 625 milliseconds per beat and 2.5 seconds per four-beat bar. It can identify C major as the relative major while preserving your original A-minor observation. The calculation does not prove the key. Instead, the observation card separates what you counted, what you heard, and why the conclusion remains provisional. You can then open the relative-key guide or use the key-signature lookup to investigate the shared signature.
Choose a route by question
If the challenge is tonal, begin with the guide to finding a song’s key. It walks through stable notes, cadences, bass motion, chord emphasis, and contrasting sections. If two services returned different labels, the disagreement guide explains why window length, enharmonic spelling, relative-key ambiguity, and modal mixture can all matter.
If the challenge is rhythmic, read the tempo, rhythm, and meter guide before calculating. It prevents a common mistake: treating BPM as a complete description of rhythmic feel. Once you have counted a repeatable span, the bars-to-tempo calculator can reproduce the arithmetic.
If the challenge is uncertainty itself, use the confidence guide. A well-supported “medium confidence” observation is more valuable than an unexplained declaration of certainty. The site encourages short evidence notes so another musician, a future version of you, or a teacher can understand how you arrived there.
What TuneReveal.com does not do
The current version is intentionally static and local. It does not accept audio files, download media, retrieve YouTube content, inspect a microphone, connect to Spotify, search a song database, or call an analysis API. It cannot verify whether the BPM, key, frequency, or meter you enter is correct. Results are educational calculations based on your inputs and conventional theory mappings.
Some music resists a single compact description. Intros may lack a clear pulse, live performances may drift, sections may modulate, and pitch standards may differ from A4 = 440 Hz. Treat every output as a working note whose usefulness depends on the observation behind it.
Frequently asked questions
Does the site analyze a song automatically?
No. You supply observations that you obtained by listening or another permitted method. The site performs only the visible browser calculation or lookup described on each tool.
Are my notes sent to a server?
No. The site has no accounts, uploads, analytics vendor, database, or persistent storage. Tool values exist only ephemerally in the active browser page.
Is a Camelot result the same as proving a key?
No. A Camelot code is a mapping from an entered conventional key. If the key observation is uncertain, the mapped code inherits that uncertainty.
Where should a beginner begin?
Read the observation-preparation guide, write down one passage and one reason for each judgment, and then open the workbench. Keep the first record small enough to revise.
Choose “Open the workbench” to record a known BPM, key, meter, confidence level, and notes. The first useful result is not a verdict. It is a clear, revisable account of what you heard and what the arithmetic says.