Correct lyrics that do not match playback

Fix lyric highlighting by validating accepted timestamp syntax, sorted cues, current playback time, and untimed fallback behavior in the browser player.

Last reviewed

The web player highlights the last parsed lyric cue whose time is at or before the current playback position. It scrolls that cue toward the center, or jumps without smooth motion when reduced motion is enabled.

Lyric timing repair workflow: compare playback time with valid cues, inspect supported timestamp syntax, upload a separate corrected test, and seek across cue boundaries.
Lyric timing repair workflow: compare playback time with valid cues, inspect supported timestamp syntax, upload a separate corrected test, and seek across cue boundaries. Open full-size screenshot.

Accepted timing syntax

A timed line must begin with [mm:ss], [mm:ss.xx], or [mm:ss:xx]. Minutes use one to three digits and seconds use exactly two. Several timestamps may precede one lyric line; Dosya creates a cue for each and sorts all cues by time. Once any timed cue parses, lines without a valid leading timestamp and metadata headers are omitted from the displayed result.

Steps

  1. Open the MP3 in the browser and choose Lyrics. Start playback at a clearly identifiable line.
  2. Compare the displayed elapsed time with the active lyric. Seeking to just before and just after the cue helps distinguish a bad timestamp from delayed audio encoding.
  3. Inspect a local copy’s embedded lyric frame. Check for missing brackets, one-digit seconds, unsupported hour fields, decimal commas, or timestamps placed after the text.
  4. Verify that lyrics are in a supported ID3 USLT/ULT frame or approved TXXX/TXX description and reachable within the first 256 KiB.
  5. Correct the timestamps locally and upload a separate test file. Reopen it and seek across several cue boundaries before replacing the original version.

Untimed and offset results

Plain fallback is all-or-nothing. If zero timed cues parse, every nonempty raw line displays at time zero without highlighting, including malformed or header-looking lines. If even one timed cue parses, only valid timed cues display; untimed lines do not remain beside them. The parser sorts out-of-order timed cues; it does not infer a global offset or compensate for silence encoded before the music.

If all cues are consistently early or late, adjust their timestamps in the source lyrics. Dosya provides no in-app lyric editor. Uploading corrected media changes cloud bytes and may affect shares using the current file, so retain the original until the test is verified.

Expected result

With timed input, each valid cue becomes active as playback crosses its parsed time and non-cue lines are absent. With zero parsed cues, all nonempty lines remain readable without synchronization. Testing and seeking do not alter the stored audio.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.

    Check the outcome before you retry

    Use these shared checks when a task needs a second look.