The goal is to Direct Play all media. This means the container, video, audio and subtitles are all compatible with the client. If the media is incompatible for any reason, Jellyfin will use FFmpeg to convert the media to a format that the client can process. Direct Stream will occur if the audio, container or subtitles happen to not be supported. If the video codec is unsupported, this will result in video transcoding. Subtitles can be tricky because they can cause Direct Stream (subtitles are remuxed) or video transcoding (burning in subtitles) to occur. This is the most intensive CPU component of transcoding. Decoding is less intensive than encoding.
|Sorted by efficency (excluding bit depth)||Chrome||Edge||Firefox||Safari||Android||iOS||SwiftFin (iOS)||AndroidTV||Roku||Kodi||Desktop|
|MPEG-4 Part 2/SP||❌||❌||❌||❌||❌||✅||❌||✅||✅||✅|
|MPEG-4 Part 2/ASP||❌||❌||❌||❌||❌||✅||❌||✅||✅|
1HEVC support is potentially available by offloading to the operating system, but this has not been tested.
2Android playback is currently broken. Client reports that HEVC is supported and attempts to Direct Stream.
3May be (partially) dependent on Hardware support (can be compensated with CPU decoding on Android). Most new Android phones in the higher price range and many "4K" AndroidTV devices have VP9 hardware decoding support. Refer to you manufacturer for supported codecs.
4AV1 support is experimental and often too slow for CPU decoding. As of writing this (05.2020) there is no hardware support on most devices yet. Support for AV1 in Jellyfin is tracked in jellyfin#3129.
5As of version 0.12, HEVC is enabled on all devices running Android 5.0+, but early generations of the Amazon Fire may not work yet. 10Bit may be supported depending on your device. Before Client 0.12, HEVC support was enabled on specific devices.
6HEVC decoding is supported on Apple devices with the A8X chip or newer and at least iOS 14
7HEVC decoding is only supported on Windows 10 with the HEVC Video Extension from the Microsoft store.
|H.262||MPEG-4 SP/ASP||H.264||MP4 Container2||H.265|
|MPEG-2 Video||DivX||MPEG-4 AVC||HEVC|
If the audio codec is unsupported or incompatible (such as playing a 5.1 channel stream on a stereo device), the audio codec must be transcoded. This is not nearly as intensive as video transcoding.
|MP2 (layer 2)||AAC (Part 7)|
|MP3 (layer 3)|
1MP3 Mono is incorrectly reported as unsupported and will transcode to AAC.
2Only EAC3 2.0 has been tested.
3OGG containers are not supported and will cause VORBIS to convert.
4Only DTS Mono has been tested.
5Safari only supports opus in
6Supported via passthrough on all devices. Native support for AC3 & E-AC3 on Roku TVs & Ultra.
ATSC Standard for AC-3 and EAC-3.
Subtiles can be a subtle issue for transcoding. Containers have a limited number of subtitles that are supported. If subtitles need to be transcoded, it will happen one of two ways: they can be converted into another format that is supported, or burned into the video due to the subtitle transcoding not being supported. Burning in subtitles is the most intensive method of transcoding. This is due to two transcodings happening at once; applying the subtitle layer on top of the video layer.
Here is a breakdown of common subtitle formats.
|SubRip Text (SRT)||Text||❌||🔶||✅||🔶|
1VTT are supported in an HLS Stream.
2DVB-SUB (SUB + IDX) is another name for VobSub files.
3EIA-608/708 subtitles are embedded in private channels (channel 21) in a MPEG video codec. EIA-608 are standard CC subtitles with the black bar background, while EIA-708 are typically SDH.
Types of Subtitles
There are many variations of subtitles. Closed, open, burned-in, forced, SDH, and CC are among the common types of subtitles. The format (such as SubRIP or VobSUB) does not matter for the type of subtitle.
This is the generic name for subtitles that can be turned on or off. This can be Forced, SDH, CC or normal subtitles.
Open subtitles (also known as burned-in subtitles) are subtitles that have been permanently placed in the video and cannot be turned off. Open subtitles are the most common type of subtitles, where the subtitles are part of the video stream and cannot be toggled on or off.
SDH and Closed Captioning
SDH and CC are subtitles for the Deaf and Hard of Hearing. They include extra content such as background noises. SDH and CC are not defined by a specific type of subtitle, just by their intent. If using an OTA Tuner and DVR, the subtitles will be embedded into the video and transcoding them before extracting the subtitles will destroy the subtitles.
"Forced subtitles are common on movies and only provide subtitles when the characters speak a foreign or alien language, or a sign, flag, or other text in a scene is not translated in the localization and dubbing process. In some cases, foreign dialogue may be left untranslated if the movie is meant to be seen from the point of view of a particular character who does not speak the language in question." - Wikipedia
To extract subtitles, the following commands can be used. The section
0:s:0 means the first subtitle, so
0:s:1 would be the second subtitle.
ffmpeg -dump_attachment:t "" -i file.mkv -map 0:s:1 -c:s ass extracted-subtitle.ass
Recorded OTA Content
Content recorded OTA will typically have subtitles embedded into the video codec itself. These subtitles are typically EIA-608 for analog and EIA-708 for digital.
ffmpeg -f lavfi -i "movie=Ronin (1998).ts[out+subcc]" -map 0:1 "Ronin (1998).srt"
If the container is unsupported, this will result in remuxing. The video and audio codec will remain intact, but wrapped in a supported container. This is the least intensive process. Most video containers will be remuxed to use the HLS streaming protocol and TS containers. Remuxing shouldn't be a concern even for an RPi3.
1MP4 containers are one of the few containers that will not remux.
2MKV containers can hold nearly any codec, but are not compatible with streaming in Firefox and will remux.
3MKV containers are improperly labeled as WebM in Firefox during playback.
4TS is one of the primary containers for streaming for Jellyfin.