Detect tuning while streaming

Streaming is where tuning claims are made and where they’re least verifiable — a “432 Hz” playlist on YouTube or Spotify is just text next to audio nobody measured. The practical answer is to check the tuning while the music plays, without downloading anything or interrupting playback. That’s what real-time detection does: it listens to whatever is coming through your browser or speakers and reports the A4 reference it hears, as it hears it.

What “detecting while streaming” means

A song’s tuning is the A4 reference pitch its notes align to — 440 Hz for the modern standard, 432 Hz for Verdi tuning, or one of the Solfeggio anchors. Real-time detection samples the notes in the audio as it plays, matches them against tuning tables for those references, and reports the anchor that fits. Analysis happens on-device; the audio isn’t uploaded anywhere, and the stream itself is untouched — you’re measuring the playback, not modifying it.

Because it works on live audio, it doesn’t matter where the music comes from. Any service you can play, you can measure.

Three ways to capture the audio

Browser tab audio

The Chrome extension can listen directly to a tab — the cleanest option for YouTube and YouTube Music. Tab capture taps the audio signal itself, so room noise, speaker quality, and volume level don’t affect the reading. Start playback, point the extension at the tab, and watch the A4 value settle.

Desktop audio

For music playing outside the browser — Spotify, Apple Music, and other desktop apps — the extension can listen to your system’s audio output instead. Same signal quality as tab capture, applied to anything your computer plays. This is the route for checking a “432 Hz” playlist in a native streaming app without moving it to the browser.

Microphone

The mic works anywhere — music from another device, a speaker across the room. It’s the most flexible capture and the most exposed to interference: room acoustics and background noise all sit between the music and the analysis. Use it when tab or desktop capture isn’t available, and expect to give it quieter surroundings and a bit more time.

If you don’t want to install anything, the free detector on the homepage supports the same three capture modes — microphone, browser tab, or desktop audio — and is a quick way to spot-check a stream before deciding you want the always-available version in your toolbar.

Reading results during playback

Live detection adds one habit on top of normal result-reading: patience with the material. A stream moves through intros, percussion breaks, and transitions where there’s little pitched content to measure. Let the detector listen through a sustained, melodic passage — a verse or a held chord progression — and watch for the reading to stabilize before you conclude anything.

• A stable value near 440 means standard tuning, whatever the title claims.
• A stable value near 432 confirms the track really is about 32 cents low — a genuine retune.
• A Solfeggio match is shown by name when the reference corresponds to one of the anchor targets.
• “Uncertain” means the current material doesn’t contain enough pitched content to justify a verdict — the detector declines to guess rather than feed you a made-up number. Skip to a more melodic section and let it try again.

The full interpretation guide, including cents offsets and in-between readings, is in how to read detection results. For squeezing the most reliable readings out of the extension specifically — capture choice, sampling time, handling noisy sources — see extension accuracy tips.

What streaming checks tend to reveal

Spend an evening measuring a “432 Hz” playlist and a pattern emerges: some tracks measure exactly as labeled, some sit at plain 440, and a few land somewhere unexpected — artifacts of pitch shifts applied without updated titles, copied descriptions, and re-uploads of re-uploads. Playlists mix reference tunings freely because curators go by titles, not measurements. None of this is visible until you measure, which is the point: real-time detection turns every stream into a checkable claim. The background on how labels drift is in why uploads are often mislabeled.

Checking while streaming is also the cheapest possible filter. Before you download, convert, or add a track to a carefully-curated tuning playlist, thirty seconds of live detection tells you whether it’s worth the trouble.

When detection isn’t enough

Detection verifies; it doesn’t change anything. If a stream measures at 440 and you wanted 432 — or a Solfeggio target — no amount of re-measuring will move it. At that point the reliable path is to retune a file you own from its measured tuning to the target, so the result doesn’t depend on any uploader’s diligence. The retuning options page covers the available tools, from a free in-browser re-tuner up to batch workflows for whole libraries.

The streaming habit worth building is short: play, capture (tab or desktop audio when you can), wait for a stable reading, and believe the number over the title. Once checking takes less time than reading the comments, there’s no reason to take a tuning label on faith again.