Audio latency check
Measures every leg between your guitar and the speaker, on this machine, in this browser. Run it, then send the result back.
| Guitar in what the interface reports | – |
| Processing block 128 frames — fixed by the browser | – |
| Output buffer the browser's own | – |
| Output device the OS and your speakers or interface | – |
| Total | – |
| What this app used to show (output side only) | – |
Use headphones. Your output is a speaker, so monitoring through it will feed back into the microphone and howl.
Every number here is reported by the browser, not measured. A true round trip needs a physical loopback — signal out of the interface, back into an input, the two waveforms compared. Treat the total as a floor: the real figure is higher, never lower.
It is the same technology from a different team. If it reports the same figures on your machine, the number is the platform's floor, not something we wrote — which is the thing we are trying to settle.
neural-amp-modeler-react.vercel.app ➚
Press Start/Resume playing, allow the microphone, then read the two lines it
prints: Base latency and Output latency. Add them together and
compare with output side only in the table above — they should match.
Play through it too, so you can compare how the two feel.