Navidrome Daily: Lyrics Timing Gets a Trust Upgrade
Two linked pull requests from contributor ranokay overhaul how Navidrome handles structured lyric timing, fixing normalization bugs that could corrupt or misrepresent lyric sources while adding new end-timing data for synced lyrics clients.
Duration: PT2M14S
Episode overview
This episode is a short developer briefing from Navidrome Daily.
It explains recent repository work in plain language.
- Show: Navidrome Daily
- Published: 2026-07-25T10:00:26Z
- Audio duration: PT2M14S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's July 25th, and today's activity centers on one thing: lyrics timing, and making sure Navidrome tells the truth about it.
Both pull requests today come from the same author, ranokay, and they build directly on each other. PR 5845 comes first, and it's the foundation: a fix for how structured lyrics get normalized. Right now, valid timing data from formats like TTML, SRT, or Lyricsfile sidecars can get lost during processing, and…
With that groundwork in place, PR 5846 adds a new capability: exposing when a synced lyric line actually ends, not just when it starts. Previously, clients had to infer line endings by looking at where the next line began, which breaks down for gaps, overlaps, or instant markers. This adds an optional end value to…
The throughline here is data integrity for structured lyrics. One PR stops bad data from masquerading as good data. The other adds richer, more precise data for clients that want it. Both trace back to the same tracking issue, number 262, suggesting a broader effort to make Navidrome's lyrics handling more…
What's next: expect client-side implementations to start consuming that new end-timing field, and worth watching whether…
That…
Nearby episodes from Navidrome Daily
- The Artwork Pipeline Rewrite Lands
- Laying Groundwork for a New Artwork Pipeline
- Foundations Work — IDs, Formatting, and Housekeeping
- Better Errors, Better Persistence
- Weekly Recap - Jellyfin Compatibility Takes Center Stage
- Jellyfin Compatibility Push
- Cover Art Gets an Overhaul
- Hardening the Jellyfin API Under Real Client Load