How automatic pitch and root-note detection works for samples

To map a sample to the right key, a sampler needs to know its pitch — the note it was recorded at, its root. Automatic pitch detection analyzes the audio and finds that fundamental frequency, so each sample lands on the correct key without you naming files or entering notes by hand. This is what lets you drop in WAVs named anything and still get a correctly tuned, correctly mapped instrument. Xampler detects pitch from the audio for every sample, in the browser, as part of building the multisample.

Try the demo — no login See what Xampler does →Pricing & credits →

In Xampler — how it maps by pitch

1Drop your WAV samples in — named anything.
2Xampler analyzes each one and finds its fundamental frequency.
3It converts that to the nearest note and uses it as the sample's root key.
4Samples tile across the keyboard, in tune — and you can override any note.

Common questions

How does a tool know what note a sample is without me telling it?

It analyzes the waveform and finds the fundamental frequency — the lowest, strongest pitch the ear hears as 'the note.' From that frequency it works out the nearest musical note and uses it as the sample's root. No file naming or manual entry needed. Xampler does this for each sample automatically.

Do I have to name my files like C3.wav, D3.wav for it to map them?

Not with pitch detection. Tools that read the note from the file name need strict naming and fail when it doesn't match — you get a 'could not detect name' error or everything maps to one key. Detecting pitch from the audio removes that requirement — name your files anything, and they still map to the right keys. This is one of the most common pain points people hit with other converters, and it's why audio-based detection is more reliable.

How accurate is automatic pitch detection?

For clear, single-note instrument samples it's very reliable — the kind of material you'd multisample (a held note, a struck key) has a strong fundamental that's easy to pin down. It's harder on noisy, chord, or heavily distorted sources, where there isn't one clear pitch. Xampler targets the single-note instrument case it's built for, and you can always override a key if a sample is ambiguous.

What if a sample is detected on the wrong octave?

Octave errors are the most common pitch-detection mistake — the fundamental versus a harmonic an octave up or down. If one sample lands an octave off, you nudge it back; the rest are usually right. Xampler maps from the detected pitch and lets you correct individual notes if needed, so a single octave slip is a quick fix, not a re-do.

Can it detect the pitch of a chord or a noisy sample?

Not reliably — a chord has several pitches at once and noise has no clear fundamental, so there's nothing single to lock onto. Pitch detection is for single-note, pitched material. For chords or textures you'd assign a key manually. Xampler is built for the single-note instrument case, which is what multisampling needs.

Does pitch detection change or tune the sample?

No — it only reads the pitch to decide which key the sample belongs on. It doesn't pitch-correct or alter the audio. The sample plays exactly as recorded on its root key; the sampler only shifts it when you play other keys. Xampler keeps your audio untouched and just maps it by the detected pitch.

Why is detecting pitch from audio better than from the filename?

Because the filename can be missing, inconsistent, or wrong, and many tools choke when it doesn't match their expected pattern. The audio always carries the true pitch. Reading it from the sound itself works no matter how the files are named, and it can't be fooled by a mislabeled file. Xampler reads the audio, so naming never blocks the mapping.