When retuning is the only safe choice

Detection and retuning solve different problems. Detection tells you what a track’s tuning actually is; retuning changes it. Whenever you need a specific tuning — not just knowledge of the current one — measurement alone eventually stops being enough, and modifying the audio becomes the only option that guarantees the result.

What detection gives you, and where it stops

The free detector at /#detector measures a song’s A4 reference — the value its notes align to — by sampling notes and matching them against tuning tables for 440 Hz, 432 Hz, and the Solfeggio anchors. It runs on-device, works from a microphone, a browser tab, or desktop audio, and says “Uncertain” when a track lacks enough pitched material rather than guessing.

That is everything detection can do. It is read-only. If the number that comes back isn’t the number you want, no amount of re-measuring will change it. The gap between “I know this track is 440” and “this track is 432” can only be closed by changing the audio, or by putting a pitch-shifting player in the playback chain.

Four situations where retuning is required

The measured tuning isn’t your target

Almost all commercial music aligns to A4 = 440 Hz, the modern standard since ISO 16 (1955). If you want 432 Hz — about 32 cents lower, where a cent is 1/100 of a semitone — or a Solfeggio anchor like 528, the audio has to be shifted. There is no shortcut that gets a 440 file to play at 432 on an ordinary player.

The label claims a tuning the audio doesn’t have

Uploads labeled “432 Hz” or “Solfeggio” frequently measure at plain 440 — platforms don’t verify tuning claims, and mislabeling is common. If you wanted what the label promised, the safe path is to take a copy of music you own and retune it yourself, from a measured starting point, rather than hunting for another upload whose label you also can’t trust.

You want a consistent Solfeggio library

A playlist assembled from mixed sources will mix references — some tracks at 440, some shifted, some already at an anchor. Bringing them all to one target means retuning each track individually from its own measured tuning; retuning a song into Solfeggio walks through that process step by step.

The music has to play correctly everywhere

Real-time retuning players can shift pitch during playback, but they only help while they’re in the loop. A retuned file, by contrast, is correct in every player, on every device — car stereo, phone, a friend’s laptop, an export to video. If the audio will travel beyond a player you control, retune the audio itself.

The unsafe alternative: blind conversion

The riskiest tool in this space is the converter that assumes every input is 440 Hz. The assumption is usually right, which is exactly what makes it dangerous — the failures are silent. Feed a genuine 432 Hz source into a 440-assuming “convert to 528” tool and the output lands off target: correct shift, wrong starting point, no warning. A conversion is only safe when it starts from the measured tuning of that specific file. A 432 Hz converter that measures first doesn’t have this failure mode.

What a safe retune looks like

Whatever tool you use, the checklist is the same:

• Measure before converting; never assume 440.
• Convert from the measured value to the target.
• Skip tracks that measured uncertain — a shift applied to an unknown starting point is still a guess.
• Keep originals untouched, so you can re-target later.
• Verify a sample of outputs by re-detecting them.

The HZ Detect desktop app for Mac and Windows builds these rules in: it batch-analyzes your library free, retunes each song from its measured tuning, never modifies originals — retuned copies are saved as WAV to a folder you choose, with disk space checked first — and excludes uncertain songs from retuning so you never pay for a guess.

When retuning isn’t necessary

Retuning is the safe choice when you need a guaranteed target, but it isn’t always needed:

• The track already measures at your target. Check first — detection takes seconds, and there’s nothing to fix if the answer matches.
• You only want to know. Curiosity is fully served by detection; keep the file as it is.
• You always listen through a real-time retuning player. HZP, on the retuning options page, retunes any song on any device during playback. Just remember that the underlying file is unchanged — outside that player, you’re back to the original tuning.

Next step

Before deciding anything, get the one fact that determines everything else: measure the track at /#detector. If the measured value matches your target, you’re done. If it doesn’t, you now know both endpoints of the retune — and a retune with both endpoints known is the only kind worth doing.