dtourolle
0f928798d7
A Jellyfin transcode is generated as it is sent — no Content-Length, Range ignored — so every interruption restarts it from byte zero, and three concurrent downloads are three ffmpeg jobs on the server. Measured on the tablet: a direct copy moves 2.06 GB in 142 s with no retries, a transcode crawls at ~1 MB/s and cannot resume. The transcode is only ever requested because of the audio track. So: always fetch Static=true, and re-encode the audio on the device when the source carries something the renderers cannot decode. DR-171 keeps its diagnosis — a downloaded film played as picture in silence, and offline there is no other source to fall back to — and loses its remedy, which explicitly accepted the loss of byte-range resumability. Its other finding survives and constrains this spec: a downloaded file outlives whatever experimentalNativeVideo was set to when it arrived, which is why the fix is to the bytes on disk rather than to one renderer. Records the rejected alternatives with the specific reason each fails, and the decision to accept HEVC staying HEVC (Android-first; recoverable by a setting, unlike silent audio).
JellyTau
A cross-platform Jellyfin client built with Tauri, SvelteKit, and TypeScript.
Business logic lives in a Rust backend; a UI-rich Svelte frontend handles presentation and talks to it over Tauri's IPC. Targets Linux (libmpv) and Android (ExoPlayer).
Getting Started
This project uses bun as its package manager.
# Activate the Rust environment (fish shell)
source "$HOME/.cargo/env.fish"
# Install dependencies
bun install
# Run in development
bun run tauri dev
# Type-check the frontend
bun run check
# Build for Linux
bun run tauri build
# Build for Android
bun run tauri android build
For the full set of build, test, and Android helper scripts, see scripts/README.md.
Documentation
| Topic | Location |
|---|---|
| Architecture overview & subsystem docs | docs/architecture/ |
| Requirements, traceability & technical debt | docs/requirements.md |
| Build & release process | docs/build/build-release.md |
| Docker builds | docs/build/docker.md |
| Traceability tooling & CI | docs/traceability.md, docs/traceability-ci.md |
| Release checklist | docs/release-checklist.md |
| UX flows | docs/ux-flows.md |
| CI operations (builder image, secrets, runner) | docs/build/ci-operations.md |
Contributing
CONTRIBUTING.md covers the setup, the gates a change has to pass, and the two rules that catch people out (bug fixes start with a failing test; Jellyfin's taxonomy stays in Rust). Please also read the Code of Conduct.
Found a security problem? Do not open an issue — see SECURITY.md.
Verifying a download
Every release publishes SHA256SUMS covering all of its artifacts, plus an SBOM
of what went into the build:
sha256sum -c SHA256SUMS
Desktop builds update themselves from Settings → Updates, verifying each payload against JellyTau's signing key before installing. Android installs are handled by the system installer, so the app links to the releases page instead.
Recommended IDE Setup
VS Code + Svelte + Tauri + rust-analyzer.
License
MIT