Navidrome Daily: Uncached Transcode Length Match and HEAD Fix
One merged fix dominates activity, with no broader pattern. Pull request 6449 matches uncached transcode output to the declared estimated length and corrects HEAD handling, addressing broken downloads linked to issue 6425.
Duration: PT1M52S
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-11-13T11:02:33Z
- Audio duration: PT1M52S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, you're listening to Navidrome Daily for November 13th, 2026.
There is no broad pattern today, just a single high-impact reliability fix for live transcoded streams that should stop broken downloads.
When the estimated content length option is enabled, Navidrome declares a size up front for an uncached transcode, but it was sending encoder output as is. If the real output ran long, the server logged an overrun error and dropped the connection. If it ran short, the connection closed before the promised length.…
That fix, in pull request sixty-four forty-nine, linked to issue sixty-four twenty-five, now matches the body to the declared length, cutting it off when needed so uncached streams stay within the HTTP contract. The author structured it as two separate fixes, one per commit, so they can be reviewed or split if…
The same update corrects handling of head requests for those streams, returning success instead of an incorrect status. That matters for API behavior because players and download tools often probe with a head request before fetching. A wrong status can block playback, break caching logic, or cause clients to mark a…
What is next is validation. If you rely on…
Nearby episodes from Navidrome Daily
- Startup Lock Fix and Scanner Test Hardening
- Uncached Transcode Reliability and Player Fixes
- Jellyfin Client Fixes and Transcoding Corrections
- Library Search Scope and Player Memory
- Jellyfin Reliability and Library-Scoped Fixes
- Weekly Recap - Jellyfin Compatibility, Input Hardening, and UI Performance
- Virtualized Libraries and Player Fixes
- Production Search Focus Fix