The short answer
A plain text lyric file supplies the words. A timed lyric file such as LRC can also include cues associating lines with points in the song. Timing is useful only when it matches the audio version you are using. The documented Visualizer prototype supports importing .txt and .lrc files, alongside audio upload and analysis. Its current public website does not verify automatic alignment, manual timing controls or export options, so this article focuses on preparing usable inputs and reviewing the resulting project.
Choose the exact song version first
A single version and an extended version can share almost every lyric while starting the first verse at different times. A longer introduction can shift every later cue. A remix may repeat a hook or cut a verse entirely. Keep the audio and lyric file associated with the same version, and name them clearly. Do not assume that lyrics pulled from another version are ready because the wording looks familiar. The relationship between the words and the recording matters as much as spelling.
Prepare readable lyric lines
Remove unrelated notes, credits or formatting that should not appear on screen. Preserve repeated lines deliberately instead of relying on shorthand that a viewer cannot understand. Break long phrases into readable units, but keep words together when splitting them would damage the meaning. Check names, slang, accents and intentional spellings against the final vocal. For a song using more than one language, proofread each part rather than letting a normalising pass remove meaningful characters.
Compare the two input types
| Input | Useful when | What still needs review |
|---|---|---|
| TXT | You have accurate words but no trusted timing | How the current editor assigns or requests line timing |
| LRC | You have line cues for the same recording | Cue accuracy, repeats and version alignment |
| Lyrics embedded in audio metadata | The prototype detects them | Whether the embedded text is complete and matches the actual vocals |
A worked example: the wrong intro length
Suppose a timed lyric file belongs to a version with a longer introduction than your release audio. Its first verse cue can arrive late, even though every word is correct. Start by comparing the first vocal entry, the first chorus and a later verse. If they all differ by the same amount, the version offset is a useful clue. If the mismatch changes later, an arrangement difference may also be involved. These are diagnostic observations; do not assume the current editor provides a particular automatic fix.
Troubleshoot timing and display separately
If lines appear at the wrong moment, investigate timing before redesigning the layout. If words appear at the correct moment but are difficult to read, examine contrast, font size, line length and how much other artwork competes with the text. Review a representative quiet verse and a dense chorus. A lyric visual also needs a clear ending: text should not remain on screen long after its phrase has ended unless that is an intentional design choice. Check the saved output with the sound on.
Common questions
Will a TXT file already know when each line starts?
Plain text alone does not supply reliable timing cues. The editor’s timing workflow must handle that separately.
Can the same LRC file work for a remix?
Only if the arrangement and cue positions still match. Review it against the actual recording.
Does detecting BPM align every lyric automatically?
No. Beat analysis and lyric placement solve different parts of the project.
What should I prepare first?
The final audio version and a complete, proofread lyric text.
Put it into practice
Explore the Visualizer preview
See the audio-visual direction and compare the looks shown on the homepage.
Plan a music release visual
Turn one release into a coherent set of visual assets.
Add a song and review its analysis
Prepare the add a song and review its analysis workflow with clear inputs and a review step.