jellyfin/jellyfin.org
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.org.git synced 2026-09-03 06:30:03 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update transcoding.md

Browse Source
This commit is contained in:
felix920506
2024-10-25 02:00:35 +08:00
parent 3532517123
commit b100beadff
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/general/server/transcoding.md
+5 -4
View File
@@ -9,10 +9,7 @@ These settings will relate to backend options that modify how the server transco
## Hardware Acceleration
If your hardware supports this you can enable [hardware acceleration](/docs/general/administration/hardware-acceleration) for much faster transcoding. Some of the supported methods are listed below.
- VAAPI
- NVENC
If your hardware supports this you can enable [hardware acceleration](/docs/general/administration/hardware-acceleration) for much faster transcoding. Some of the supported methods are listed below. Jellyfin supports hardware accelerated transcoding on all modern GPUs from Intel, AMD, Nvidia, Apple, Rockchip and Raspberry Pi if the required hardware is available.
## Thread Count
@@ -26,3 +23,7 @@ There are four types of playback; three of which involve transcoding. The type b
- Remux: Changes the container but leaves both audio and video streams untouched.
- Direct Stream: Transcodes audio but leaves original video untouched.
- Transcode: Transcodes the video stream.
## HDR to SDR Tone-mapping
When the source video is in HDR, it will need to be tone-mapped to SDR when transcoding, as Jellyfin currently doesn't support HDR to HDR tone-mapping, or passing through HDR metadata. While this can be done in software, it is very slow and you may encounter situations where no modern consumer CPUs can transcode in real time. Therefore, a GPU is always recommended, where even a basic Intel iGPU can handle the load without problems.