jellyfin-ffmpeg

mirror of https://github.com/jellyfin/jellyfin-ffmpeg.git synced 2026-09-02 21:03:08 +03:00

Table of Contents

Why Some Changes Stay Here
What We Still Upstream
What This Means for You

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

We regularly evaluate upstreaming changes. In practice, our approach is:

Bug fixes: Upstreamed when feasible and aligned with upstream direction.
Targeted features: Maintained in this fork when upstream priorities differ or review bandwidth is limited, especially for hardware‑specific features.

Why Some Changes Stay Here

Different priorities: Upstream FFmpeg focuses on broad portability and a wide range of use cases. Jellyfin‑FFmpeg prioritizes practical server workflows (HDR/Dolby Vision playback, hardware acceleration pipelines, streaming reliability).
Long review cycles: Some feature patches—particularly hardware‑specific ones—can sit without review for months, or indefinitely.
Implementation trade‑offs: Certain implementation approaches (e.g., heavy SIMD intrinsics use in the tonemapx filter) may face strong stylistic or architectural objections upstream despite clear benefits in Jellyfin use cases.
Legacy constraints: Upstream must keep building across very old CPUs, compilers, and OS versions. We do not carry that burden. Running a media server like Jellyfin on such old platforms that even the hardware vendor drops support is not practical.

What We Still Upstream

We continue to propose and upstream bug fixes where they fit upstream’s goals.
When a feature patch matures and aligns with upstream’s direction, we’re open to contributing it. Until then, we keep it here for Jellyfin users who need it now.

What This Means for You

Jellyfin‑FFmpeg likely reduces issues and improves performance for Jellyfin playback.
If your needs are basic and upstream FFmpeg already works well, you can keep using it.