How to Fix Out-of-Sync VTT and LRC Subtitles in Long Audio
A practical checklist for fixing subtitle drift in VTT and LRC tracks, including offsets, cue gaps, long-file timing, and player-side sync.
Drift is the most common subtitle complaint. The first line looks perfect, then the text slowly moves ahead of the voice until the translation is useless. The cause is not always a bad subtitle file; it can be an offset, a player that ignores cue end times, or a conversion that changed the timing base.
Work through the checks below in order. Most tracks can be fixed without rebuilding the entire subtitle file.
1. Check for a constant offset first
If every line is early or late by the same amount, you have an offset problem, not a drift problem. Note the difference at the start of the track and apply a single global delay in the player or editor. Do not start moving individual cues yet.
- Play the first spoken line and note how early or late the caption appears.
- Apply a global subtitle delay of that amount.
- Jump to the middle and the end to confirm the offset stayed constant.
2. Distinguish offset from progressive drift
Progressive drift means the gap grows over time. That usually points to a different timing base, a frame-rate conversion, or edits made to the audio after the subtitles were timed. If the gap at 60 minutes is much larger than the gap at 5 minutes, a global offset will not fix it.
Compare the subtitle timestamps against the actual audio duration. If the subtitle file was timed to a different edit, the cue map needs to be retimed rather than nudged.
3. Check cue end times and gaps
LRC has no explicit end time, so a missing timestamp can make a line linger too long or vanish too early. VTT can have the opposite problem: a cue that ends before a slow line finishes. Look for unusually large gaps, zero-length cues, and lines that overlap in a way the player cannot render.
- Remove duplicate timestamps that point to the same line.
- Give long pauses their own empty cue instead of stretching the previous line.
- Keep bilingual pairs on the same cue so they appear and disappear together.
4. Verify encoding and line endings
Japanese text should be saved as UTF-8. A file saved in a legacy encoding may show garbled characters, and some players will drop the entire cue rather than display broken text. Windows line endings are usually tolerated, but mixed line endings can confuse simple parsers.
5. Use a player that renders against the audio clock
Some players advance subtitles with a separate timer that does not stay aligned with the audio device. The result is drift that gets worse during long files or after seeking. A player that renders cues against the active audio clock, and re-syncs after every seek, avoids this class of bug.
AI Audio Player Pro is built around that model: it loads VTT or LRC timing, keeps the original cue boundaries, and renders the translation at the same moment as the source line.
6. Test at the edges, not only the start
A track can look perfect at 00:30 and fall apart at 01:20:00. Check at least three points: the first minute, the midpoint, and the final two minutes. If all three stay aligned, the track is ready for a full listen.
Frequently asked questions
Why do subtitles drift more in long ASMR files?
Long files expose small timing-base differences and player clock errors. A gap that is invisible in a three-minute track can grow into several seconds over an hour.
Can a global subtitle delay fix drift?
It fixes a constant offset only. If the gap grows over time, the file needs retiming or the player needs a clock-accurate rendering path.
Should I edit the subtitle file or adjust the player?
Try the player's global offset first. Edit the file only when the cue map itself is wrong.
Read the line, then hear it
AI Audio Player Pro plays your audio with synced VTT or LRC captions and real-time English translation.