A labs.llc instrument
Every note,
on every tuning.
A fretboard computed, not drawn: eleven tunings, fourteen scales, sixteen chord types.
Click any fret to hear a modelled string. A microphone tuner sits below.
The neck
Pick a key and look at it
In this key
What fits the key you picked
Four panels follow the neck above. Click anything to hear it.
The tuner
Play one string
Autocorrelation on the waveform, so a weak low-E fundamental is not read as its octave. About a cent of resolution.
The manual
How it is built
There are no chord diagrams
A tuning is six MIDI numbers, a scale a set of semitone offsets, a fret is open + n. Every dot falls out of that, so another tuning is one line in js/theory.js.
Shapes are searched, not stored
For each four-fret window the page keeps only chord tones, then scores muted strings, reach, fingers and a root in the bass. Cm in DADGAD is found the same way as in standard.
Positions are cut by notes per string
Three per string for seven-note scales, two for five and six. Each string starts on the first scale note above the last one on the string below.
The circle is one multiplication
A key sits at its pitch class × 7 mod 12. One to six steps either way is the number of sharps or flats, and the relative minor shares the slot.
The string is rendered, not looped
A Web Audio delay inside a feedback loop is clamped to 128 samples, which pins every note above F4. So the string is rendered in JavaScript with a fractional delay line, exact at every fret.
Why the frets look right
Fret n sits at 1 − 2^(−n/12) of the scale length. Even spacing is what makes a drawn neck look wrong.
The tuner
Normalised square difference, the first peak over threshold rather than the global maximum, and parabolic interpolation on the winning lag. That is the difference between five cents and one.
The microphone
Requested when you turn the tuner on and released when you turn it off. Frames are measured and discarded; there is no server to send them to.