Compare two recordings of the same event and estimate how far the second recording is shifted in time.
Audio is processed locally in your browser and is not uploaded.
Compare two recordings of the same event and estimate how far the second recording is shifted in time.
Browser results depend on device resources and supported codecs. Use short or medium files for responsive processing.
Common MP3, WAV, M4A/AAC, Ogg, FLAC, and WebM files may work when the current browser can decode them. Recording output depends on MediaRecorder support. Generated tones export as PCM WAV.
Begin with a short, clean file so you can verify the result quickly. For analysis tools, compare the result with what you hear rather than treating one number as a final mastering decision. Keep headphone volume moderate when generating tones.
Use recordings that contain the same recognizable sound, preferably near the start of both files.
The estimate uses downsampled waveform correlation, so it is intended for practical alignment rather than forensic measurement.
It means the comparison recording appears later than the reference and should be moved earlier by that amount.
Different content, noise, long silence, echo, or drift can weaken correlation.
No. It estimates one fixed offset; changing drift over time needs a separate correction workflow.
| Privacy | Local browser processing |
|---|---|
| Tool number | 123 |
| Category | Speed Pitch & Timing |
| Output | Actual report, labels, recording, or WAV file |