Liner Notes
Markdown kept next to the music, about a track, a release, an artist, or one particular
playing. Edited in place with every earlier version archived. Rendered and sanitised
server-side, so shortcode resolution happens in the same pass and notes are safe to display
anywhere.
Searchable across both what you wrote and what you wrote it about, filterable by kind,
sortable by edit, by date written or alphabetically.
Loved
Every heart in one place — tracks, records and artists, since a love attaches to an
entity rather than only a song. A recording love mirrors out to Last.fm and ListenBrainz;
albums and artists stay local because neither service has the concept.
Loves you already have on those services can be pulled back in from Settings →
Connections. The star ratings sitting in Plex, Navidrome, Jellyfin or Emby become loves
from Settings → Ratings, above a threshold you set in five or ten stars, halves or whole.
Each rating is kept exactly as the server gave it, beside what it was out of, and the
threshold is applied to the fraction. So four out of five is the same verdict as eight out
of ten, and a Plex 7 does not clear either. Raising the threshold takes back only the loves
it made. A love you pressed yourself is outside its reach, and nothing it does is forwarded
to Last.fm or ListenBrainz.
Lyrics
Read from your own Plex or Jellyfin first, from LRCLIB after that, and words you type in
yourself outrank both. They are fetched at all for one reason: script detection settles any
non-Latin title and gives up on a romanised one. Three outcomes, all real answers — a language by script weight, instrumental when the track has no words, or nothing at all for a Latin lyric,
because guessing French is the mistake the fidelity cards were fixed for.
Cached outside the backup, never redistributed. A note quotes a line by index,
never by its words.
When words are present there is a lyrics theatre — current line large, the
rest falling away, following the clock when they're timed. It exists for the listening you
can't touch: a side is playing and your hands are on a record.
Whichever record is held, Other versions lists what else LRCLIB has for the track
— script, timed or plain, line count against the one held, length against the track — and a
pick is credited to LRCLIB rather than to you, which a correction you type still is.
Lyrics in letters you read
A song in a script you don't read is words you can't follow along to. So the reader has an Original / Romanized / Both toggle, and Both sets the Latin
letters under their own line, word above word. Romanization is written natively in Rust —
no Python and no subprocess — and produced per line as the lyric was numbered, so a [[line:12]] quote still points at line 12.
There is a worked example on the home page — six of the
twelve, every phrase in it taken from the romanizer's own tests.
Twelve languages, not every language. Korean, Japanese and Chinese; Hindi,
Bengali, Punjabi, Gujarati, Tamil, Telugu, Kannada and Malayalam; Russian. Arabic, Hebrew,
Thai, Greek and the Cyrillic of Russian's neighbours are left as they were written — a
Ukrainian or Serbian line read with Russian's rules would be wrong in a way you couldn't
see, so it isn't read at all.
It is read as sung where the rules allow: Korean takes Revised Romanization after
the standard pronunciation rules, with liaison and assimilation applied, and Tamil voicing
and Hindi schwa deletion are in the readable style. Russian is spelled as written rather
than as sung, because reading it as sung needs the stress, which is a dictionary and not a
rule.
Two styles, your choice
Readable, or strict
Indian scripts: ISO 15919 exactly, or lyric-site spelling. Russian: Wikipedia's spelling,
or ISO 9 — one Latin letter per Cyrillic one. Japanese macrons are their own switch, and
the choice sits in Settings.
A romanised lyric in your own files
Keep the original beside it
Tags that hold a romanised lyric can keep LRCLIB's own-script record as a companion, and
it is used only while the two line up — same line count, cues within two seconds. There
is nothing to romanize from Latin letters; the companion is what gets romanized.
Shipped in the binary
The dictionaries cost size
Japanese and Chinese need a tokeniser and a dictionary each: about 72 MB of binary, and
roughly 20 MB resident while in use — measured on a Pi 5. Built without them, kana is
still romanized and ideographs are left as written.