Navidrome Daily: Trusting What the Client Sees
Two merged fixes this cycle both target accuracy of what's delivered to the client — one correcting misleading audio quality metadata in transcoded streams, the other ensuring browsers don't run stale front-end code after an upgrade.
Duration: PT2M19S
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-13T10:00:15Z
- Audio duration: PT2M19S
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 13th, 2026, and this is Navidrome Daily.
Today's theme is trust — making sure what the client receives matches what's actually true, whether that's audio quality data or the web app itself.
Start with PR 5768 from Deluan. The transcode decision logic was copying a source file's bit depth straight into the response, even when the target format made that number meaningless. A 24-bit FLAC transcoded down to Opus was reporting a bit depth of 24 — and some clients read that as a signal of quality, showing…
Second theme: stale clients after deployment. PR 5767, from apkatsikas, addresses issue 5766 — browsers were caching index dot HTML using heuristic rules, so after an upgrade, users could keep loading an old version of the page that references JavaScript assets which no longer exist on the server. The fix sets…
Both changes are small in scope, but they share a root cause: assumptions in the code that didn't match reality — copied metadata that didn't apply, and caching behavior that didn't account for deploys.
Nothing else notable landed. What to remember: if you rely on audio bitdepth as a quality signal client-side, expect it to be absent now for lossy streams…