TuneHaven

Why your tuner keeps jumping to a different string

You are tuning the A string and the display suddenly says D. That is not the tuner hearing better than you, it is the tuner guessing, and the guess is what sends you tuning the wrong string in the wrong direction.

You pluck the A string. It is flat, so you start tightening. Halfway there the display flips to D, and now the needle says you are sharp. Tighten or loosen? You genuinely cannot tell any more, and whichever you pick, you are following a machine that changed its mind about what you were doing.

This is the most common complaint about tuners, and it is not a hardware defect. It is a design decision, made badly.

What is actually happening

Most tuners in auto mode work like this: detect a frequency, then find whichever string in the current tuning is nearest to it, then display the offset from that string.

The failure is in “whichever is nearest”. If your A string at 110 Hz has drooped a long way, or if the detector momentarily reads a harmonic instead of the fundamental, the nearest target can flip to a different string. The tuner does not know you have been working on the A for the last thirty seconds. It has no memory of your intent. Every reading is a fresh guess, and adjacent guitar strings are only five semitones apart, so the guesses collide constantly.

It gets worse on instruments with strings tuned in unisons or octaves. On a 12-string guitar, a mandolin or an oud, two strings are supposed to give the same reading, so “nearest string” is ambiguous by construction.

Why the fix is not “just be more accurate”

You cannot solve this with a better pitch detector, because the pitch detection is often fine. The detector correctly reported 130 Hz. The bug is that the tuner then decided, on its own, that 130 Hz meant you had switched to the D string.

The fix is to stop the tuner making that decision unilaterally.

What TuneHaven does instead

Three things, and they are the reason the app exists in this shape.

It does not switch the string you selected. If you pick the A string, the meter stays on the A string. It will tell you when what it hears looks much more like a different string, because that information is useful, but the suggestion is offered and you decide. It never quietly reassigns your target mid-adjustment and inverts the direction you should be turning.

It rejects octave candidates rather than trusting the loudest peak. A great many of these apparent string jumps are really octave errors, where the detector grabbed a harmonic. Filtering those removes a large fraction of the flapping outright.

It refuses to answer when it cannot hear you properly. In a noisy room, or when a note has decayed to almost nothing, the honest answer is “I cannot tell”, not a confident number that happens to be wrong. A tuner that always shows something is not more capable, it just never admits the times it is guessing.

What you can do with any tuner

If you are stuck with one that jumps:

  • Use manual string selection if it has one. It turns off the guessing entirely.
  • Pluck over the neck, not the bridge, which emphasises the fundamental over the harmonics.
  • Give the note a moment. Read the display after the attack has passed rather than during it. The first fraction of a second of a plucked note is the least stable part of it.
  • Damp the strings you are not tuning. Sympathetic ringing from neighbouring strings is a real source of confusion, especially on doubled courses.