From c29d801d38f0ce1d3c824b096b71f418a734557d Mon Sep 17 00:00:00 2001 From: felix920506 Date: Mon, 22 Jul 2024 01:51:15 +0800 Subject: [PATCH] hopefully make linter happy --- .../hardware-acceleration/amd.md | 26 +++++------ .../hardware-acceleration/intel.md | 16 +++---- .../hardware-acceleration/known-issues.md | 43 +++++++++---------- 3 files changed, 41 insertions(+), 44 deletions(-) diff --git a/docs/general/administration/hardware-acceleration/amd.md b/docs/general/administration/hardware-acceleration/amd.md index b86fcb772..939f3d454 100644 --- a/docs/general/administration/hardware-acceleration/amd.md +++ b/docs/general/administration/hardware-acceleration/amd.md @@ -123,7 +123,7 @@ Windows 10 64-bit and newer is recommeded. **AMF is not available in Windows Doc ### Known Issues And Limitations On Windows -Please refer to [this section](/docs/general/administration/hardware-acceleration/known-issues#windows) for known issues and limitations. +Please refer to [this section](/docs/general/administration/hardware-acceleration/known-issues#amd-on-windows) for known issues and limitations. ### Configure On Windows Host @@ -181,7 +181,7 @@ A 64-bit Linux distribution is required. **The supported GPU varies by kernel an ### Known Issues And Limitations On Linux -Please refer to [this section](/docs/general/administration/hardware-acceleration/known-issues#linux) for known issues and limitations. +Please refer to [this section](/docs/general/administration/hardware-acceleration/known-issues#amd-on-linux) for known issues and limitations. ### Configure On Linux Host @@ -257,17 +257,17 @@ Root permission is required. `VAEntrypointVLD` means that your card is capable to decode this format, `VAEntrypointEncSlice` means that you can encode to this format. - | Jellyfin Setting | VA-API Profil | - |------------------|-------------------------------------------------------------------------------------------------------| - | H264 | VAProfileH264Baseline
VAProfileH264Main
VAProfileH264High
VAProfileH264ConstrainedBaseline | - | HEVC | VAProfileHEVCMain | + | Jellyfin Setting | VA-API Profil | + | ---------------- | ------------------------------------------------------------------------------------------------------ | + | H264 | VAProfileH264Baseline
VAProfileH264Main
VAProfileH264High
VAProfileH264ConstrainedBaseline | + | HEVC | VAProfileHEVCMain | | MPEG2 | VAProfileMPEG2Simple
VAProfileMPEG2Main | - | VC1 | VAProfileVC1Simple
VAProfileVC1Main
VAProfileVC1Advanced | - | VP8 | VAProfileVP8Version0
VAProfileVP8Version1
VAProfileVP8Version2
VAProfileVP8Version3 | - | VP9 | VAProfileVP9Profile0 | - | AV1 | VAProfileAV1Profile0 | - | HEVC 10bit | VAProfileHEVCMain10 | - | VP9 10bit | VAProfileVP9Profile2 | + | VC1 | VAProfileVC1Simple
VAProfileVC1Main
VAProfileVC1Advanced | + | VP8 | VAProfileVP8Version0
VAProfileVP8Version1
VAProfileVP8Version2
VAProfileVP8Version3 | + | VP9 | VAProfileVP9Profile0 | + | AV1 | VAProfileAV1Profile0 | + | HEVC 10bit | VAProfileHEVCMain10 | + | VP9 10bit | VAProfileVP9Profile2 | 6. Check the Vulkan runtime status: @@ -436,7 +436,7 @@ Root permission is required. image: jellyfin/jellyfin user: 1000:1000 group_add: - - "122" # Change this to match your "render" host group id and remove this comment + - '122' # Change this to match your "render" host group id and remove this comment network_mode: 'host' volumes: - /path/to/config:/config diff --git a/docs/general/administration/hardware-acceleration/intel.md b/docs/general/administration/hardware-acceleration/intel.md index 375af1f51..a82e532ea 100644 --- a/docs/general/administration/hardware-acceleration/intel.md +++ b/docs/general/administration/hardware-acceleration/intel.md @@ -221,7 +221,7 @@ Windows 10 64-bit and newer is recommeded. **QSV is not available on Windows Doc ### Known Issues And Limitations On Windows -Please refer to [this section](/docs/general/administration/hardware-acceleration/known-issues#windows-1) for known issues and limitations +Please refer to [this section](/docs/general/administration/hardware-acceleration/known-issues#intel-on-windows) for known issues and limitations ### Configure On Windows Host @@ -277,7 +277,7 @@ A 64-bit Linux distribution is required. **The supported GPU varies by kernel an ### Known Issues And Limitations On Linux -Please refer to [this section](/docs/general/administration/hardware-acceleration/known-issues#linux-1) for known issues and limitations +Please refer to [this section](/docs/general/administration/hardware-acceleration/known-issues#intel-on-linux) for known issues and limitations ### Configure On Linux Host @@ -528,7 +528,7 @@ What you need to do is pass the host's `render` group id to Docker and modify th image: jellyfin/jellyfin user: 1000:1000 group_add: - - "122" # Change this to match your "render" host group id and remove this comment + - '122' # Change this to match your "render" host group id and remove this comment network_mode: 'host' volumes: - /path/to/config:/config @@ -589,19 +589,19 @@ The devices in Kubernetes are added as host path mounts, they are not separated supplementalGroups: - 122 # Change this to match your "render" host group id and remove this comment containers: - - name: "jellyfin" + - name: 'jellyfin' image: ... ports: ... env: ... securityContext: privileged: true # Container must run as privileged inside of the pod volumeMounts: - - name: "render-device" - mountPath: "/dev/dri/renderD128" + - name: 'render-device' + mountPath: '/dev/dri/renderD128' volumes: - - name: "render-device" + - name: 'render-device' hostPath: - path: "/dev/dri/renderD128" + path: '/dev/dri/renderD128' ``` 2. When the pod starts, you can check the QSV and VA-API codecs. diff --git a/docs/general/administration/hardware-acceleration/known-issues.md b/docs/general/administration/hardware-acceleration/known-issues.md index 59211d3d7..11a4de814 100644 --- a/docs/general/administration/hardware-acceleration/known-issues.md +++ b/docs/general/administration/hardware-acceleration/known-issues.md @@ -2,45 +2,42 @@ uid: admin-hardware-acceleration-issues title: Known Issues --- + # Known Hardware Acceleration Issues and Limitations This page lists all known issues and limitations of hardware acceleration with Jellyfin. -## AMD - -### Windows +## AMD on Windows 1. AMD Radeon RX 5000 and newer RDNA series integrated and discrete GPUs have an Windows graphics driver issue ranging from **Adrenalin 24.1.1 to 24.4.1**. You may experience **playback failure** and observe an **error code of `-60`** in the FFmpeg log when transcoding and playing videos. The driver **Adrenalin 24.5.1** and newer drivers fix this issue. -### Linux +## AMD on Linux 1. Some Linux distros intentionally disabled the H.264 and HEVC codecs from the Mesa VA-API driver. - Known affected distros: - - - [Fedora](https://www.phoronix.com/news/Fedora-Disable-Bad-VA-API) + Known affected distros: - - [OpenSUSE](https://www.webpronews.com/fedora-and-opensuse-disable-gpu-accelerated-video-over-patent-concerns/) + - [Fedora](https://www.phoronix.com/news/Fedora-Disable-Bad-VA-API) - - [Manjaro](https://forum.manjaro.org/t/stable-update-2022-12-06-kernels-mesa-plasma-cinnamon-nvidia-libreoffice-pipewire-virtualbox/128453) + - [OpenSUSE](https://www.webpronews.com/fedora-and-opensuse-disable-gpu-accelerated-video-over-patent-concerns/) - This prevents you from using the AMD VA-API transcoding **on the server system**. + - [Manjaro](https://forum.manjaro.org/t/stable-update-2022-12-06-kernels-mesa-plasma-cinnamon-nvidia-libreoffice-pipewire-virtualbox/128453) - You can use our Docker image instead or install third-party Mesa driver package. + This prevents you from using the AMD VA-API transcoding **on the server system**. - Alternatively, rebuild the Mesa driver with these options added to restore the stripped hardware codecs: + You can use our Docker image instead or install third-party Mesa driver package. - ```shell - -D video-codecs=all - ``` + Alternatively, rebuild the Mesa driver with these options added to restore the stripped hardware codecs: -## Intel + ```shell + -D video-codecs=all + ``` -### Windows +## Intel on Windows 1. Intel 11th Gen and newer UHD, Xe and ARC series integrated and discrete GPUs have an Windows graphics driver issue ranging from **31.0.101.5186 / 31.0.101.5234 to 31.0.101.5534**. You may encounter a **green or blue screen but normal sound** when transcoding and playing HDR videos that **require tone-mapping**. The **31.0.101.5590** and newer drivers fix this issue. -### Linux +## Intel on Linux 1. Intel Gen 11 [**Jasper Lake**](https://ark.intel.com/content/www/us/en/ark/products/codename/128823/products-formerly-jasper-lake.html) and [**Elkhart Lake**](https://ark.intel.com/content/www/us/en/ark/products/codename/128825/products-formerly-elkhart-lake.html) platforms (e.g. N5095, N5105, N6005, J6412) have quirks when using video encoders on Linux. The [Low-Power Encoding](/docs/general/administration/hardware-acceleration/intel#low-power-encoding) mode MUST be configured and enabled for correct VBR and CBR bitrate control that is required by Jellyfin. @@ -87,8 +84,8 @@ This page lists all known issues and limitations of hardware acceleration with J Consumer targeted [Geforce and some entry-level Quadro](https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new) cards have an artificial limit on the number of concurrent NVENC encoding sessions. This restriction can be circumvented by applying an [unofficial patch](https://github.com/keylase/nvidia-patch) to the NVIDIA Linux and Windows driver. -| NVIDIA driver | NVENC concurrent sessions | -| -------------- | ------------------------- | -| 550 and newer | Up to 8 encoding sessions | -| 530 to 546 | Up to 5 encoding sessions | -| pre-530 | Up to 3 encoding sessions | +| NVIDIA driver | NVENC concurrent sessions | +| ------------- | ------------------------- | +| 550 and newer | Up to 8 encoding sessions | +| 530 to 546 | Up to 5 encoding sessions | +| pre-530 | Up to 3 encoding sessions |