A wrong LRC file result usually needs a corrected start timestamp or interval, a regenerated preview, and individual retiming in a dedicated editor against the exact recording.
Begin by deciding whether the preview itself is wrong or whether it is correct but the target player behaves differently. The LRC File Generator formats the lyric rows and timing values you provide; it does not listen to audio, detect sung lines, transcribe vocals, or align words automatically. Its fixed interval is a starting draft, so a file can have perfectly regular timestamps and still feel wrong against the recording.

Triage the symptom before changing anything
Use the symptom to identify the layer that needs attention. A malformed preview points to the supplied inputs or generation process, while a correct preview that behaves badly in a player points to compatibility or remaining timing differences.
| What the result shows | What to check | Correction |
|---|---|---|
| The first lyric appears early or late. | The first MM:SS.xx timestamp and the recording version. | Change the first timestamp, regenerate, and confirm the first line appears at the vocal onset. |
| The lines are evenly spaced but gradually drift out of sync. | The single fixed interval applied to every successive line. | Choose a more suitable starting interval, then retime individual lines in an editor. |
| Words, punctuation, capitalization, or language look wrong. | The original lyric rows. | Correct the input and regenerate. The generator preserves ordinary lyric text rather than rewriting it. |
| Title, artist, or album information looks wrong. | The optional ti, ar, and al metadata tags. | Re-enter the relevant field and regenerate the preview. |
| A timestamp is malformed or generation stops. | The timestamp syntax and the calculated final time. | Correct the format or adjust the start time, interval, or number of lines. |
| The preview is correct, but the player does not display it correctly. | The player's supported LRC features. | Finish the timing pass, save the UTF-8 .lrc file, and test it in the target player. |
Inspect the first and last timestamps as an initial boundary check. They can expose a bad start value, an unrealistic interval, or a result near the maximum supported time. However, plausible endpoints do not prove that the middle lines match the vocal performance.
Fix the result in the Create LRC File workflow
Use this repair sequence within the Create LRC File workflow. It creates a valid draft first; the final vocal-level timing pass takes place after download.
- Prepare the source lyrics. Keep a plain-text copy so you can compare it with the result. The generator preserves ordinary lyric text, including spelling, punctuation, capitalization, language, and copyright notices.
- Enter the display events. Paste the lyrics in their intended order, using one non-empty lyric line for each display event. The accepted range is 1–500 non-empty lines. Blank rows are removed, each line may contain up to 500 characters, and the lyric input may contain up to 50,000 characters. Disallowed control characters are rejected.
- Set the first timestamp. Use the exact form MM:SS.xx. It must contain two or three minute digits, exactly two second digits from 00 through 59, a period, and exactly two centisecond digits. Valid examples include 00:00.00, 09:59.99, 10:00.00, and 123:45.67.
- Choose the interval. Enter a value from 0.01 through 600.00, with no more than two decimal places. This value sets the gap between every successive line. Treat it as an estimate rather than measured vocal timing.
- Add metadata only when needed. Optional title, artist, and album values become the ti, ar, and al tags. Each value is trimmed and limited to 120 characters. Square brackets and control characters are not allowed, while empty fields are omitted.
- Generate and inspect the complete preview. Check that every timed row has a bracketed timestamp immediately followed by its lyric. Review the first and last timestamps, the optional tags, and every line for unexpected spacing or missing text.
- Correct the inputs and regenerate. If the preview is wrong, edit the relevant lyric, timestamp, interval, or metadata field. Editing any input clears the previous preview, so generate it again before downloading.
- Download and finish the timing. The download saves the exact preview as UTF-8 text with an .lrc extension and no added byte-order mark. Open the downloaded file in a dedicated editor or the target player/editor, adjust individual timestamps against the exact recording, and test the completed result.
Check the values that can invalidate the output
When the preview is malformed, compare every control with the generator's accepted values before assuming the player caused the problem.
| Input or output item | Accepted value | Why it matters |
|---|---|---|
| First timestamp | Two or three minute digits, two second digits from 00–59, a period, and exactly two centisecond digits. | An invalid first value prevents the expected simple LRC output from being generated. |
| Interval | 0.01–600.00, with no more than two decimal places. | The value is converted to integer centiseconds before row timestamps are calculated. |
| Lyric input | 1–500 non-empty lines, up to 50,000 input characters, and up to 500 characters per line. | Blank rows are removed, while disallowed control characters are rejected. |
| Metadata | Optional title, artist, and album values of no more than 120 characters after trimming, without square brackets or control characters. | Only ti, ar, and al tags are emitted. |
| Final calculated timestamp | No later than 999:59.99. | If it would exceed that limit, generation fails instead of silently truncating the timestamp. |
| Downloaded file | UTF-8 text without a byte-order mark, using the same text shown in the preview. | Players may still differ in how they recognize encodings, tags, and long timestamps. |
Converting the interval to integer centiseconds before producing the rows prevents binary floating-point drift during repeated additions. That makes the output repeatable, but it does not make equal spacing correct for a real performance.
The interpretation is consistent with Subforge's LRC time implementation, which assigns 60,000 milliseconds to a minute, 1,000 milliseconds to a second, and treats two fractional digits as centiseconds.
Retime individual lines against the recording
The Create LRC File controls accept a first timestamp and one interval, not a separate timestamp for every line. For performance-level accuracy, open the downloaded draft in a dedicated LRC editor or use a timing editor in the target player/editor.
- Play the exact recording and identify the moment the first sung line begins. Set that line's timestamp to that point.
- Move through the lyric rows in display order and replace each timestamp with the point at which its corresponding line begins.
- Replay instrumental breaks, repeated phrases, and transitions to make sure each change occurs at the intended vocal onset.
- Save the edited file, reopen it in the target player, and confirm that the displayed lines advance with the recording.
Keep this manual pass separate from the fixed-interval draft. Re-entering the lyrics into the generator would rebuild the regular timeline rather than reproduce the individual edits.
Separate simple LRC support from enhanced features
LRC is a de-facto family of formats rather than one official universal standard. QuickLRC's overview of the LRC format describes the broader format landscape, while this generator deliberately stays within a conservative simple subset.
- It does not emit hour fields.
- It does not use colon-separated frame timestamps.
- It does not use three-digit millisecond timestamps.
- It does not emit enhanced word-level angle-bracket timestamps.
- It does not emit karaoke duet markers.
- It does not emit player-specific extensions.
Music players also differ in their handling of metadata tags, timestamp precision, encodings, long minute values, and enhanced-LRC extensions. If the target player requires enhanced LRC, use a dedicated editor or workflow that supports that format. If the preview is correct but ignored, verify that the player is loading the generated .lrc file for the exact recording. The filename comes from the title when one is available; unsafe punctuation becomes hyphens, and a blank title uses synced-lyrics.lrc.
Confirm the repaired result
Before replacing the original draft, run this final check:
- The downloaded text matches the generator preview.
- The first and last timestamps represent the intended boundaries.
- Every timed row contains one timestamp immediately followed by its lyric.
- Only the optional title, artist, and album tags are present.
- Individual vocal onsets have been checked and adjusted in an editor.
- The completed UTF-8 .lrc file displays correctly in the target player.
The generator does not supply or license lyrics, so reproduce and distribute only lyric text you have permission to use.
If you're weighing options, Online Metronome Mistakes: Symptoms, Causes, and Fixes covers this in detail.
If you're weighing options, How Do I Generate an LRC File With Create LRC File? covers this in detail.