+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: 4k HEVC Playback Issues in Browser (/t-4k-hevc-playback-issues-in-browser)
4k HEVC Playback Issues in Browser - tbrewst - 2024-09-05
I'm having an issue getting 4K HEVC movies to play in browser on an M1 Macbook Pro and an older Samsung TV.
I'm not having playback issues on my phone, my Intel Macbook, or my LG TV.
In Chrome, it gives me the fatal error notification.
In Safari, it endlessly loads.
Here's the log where it's clear there's an error, I just don't know how to proceed:
ffmpeg version 6.0.1-Jellyfin Copyright © 2000-2023 the FFmpeg developers
built with gcc 12 (Debian 12.2.0-14)
configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-ptx-compression --disable-static --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto --enable-gpl --enable-version3 --enable-shared --enable-gmp --enable-gnutls --enable-chromaprint --enable-opencl --enable-libdrm --enable-libxml2 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libsvtav1 --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=amd64 --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-vaapi --enable-amf --enable-libvpl --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc
libavutil 58. 2.100 / 58. 2.100
libavcodec 60. 3.100 / 60. 3.100
libavformat 60. 3.100 / 60. 3.100
libavdevice 60. 1.100 / 60. 1.100
libavfilter 9. 3.100 / 9. 3.100
libswscale 7. 1.100 / 7. 1.100
libswresample 4. 10.100 / 4. 10.100
libpostproc 57. 1.100 / 57. 1.100
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
[AVHWDeviceContext @ 0x558802d44e40] Failed to get number of OpenCL platforms: -1001.
Device creation failed: -19.
Failed to set value 'opencl=ocl@va' for option 'init_hw_device': No such device
Error parsing global options: No such device
RE: 4k HEVC Playback Issues in Browser - Efficient_Good_5784 - 2024-09-05
Looks like you did it too while I was doing it, but I edited your post to change the text color to be white (couldn't see the black color text on the forum).
Can you provide what system specs you're using and what your transcoding settings looks like? Seems like you don't have the GPU passed correctly to Jellyfin.
RE: 4k HEVC Playback Issues in Browser - TheDreadPirate - 2024-09-05
Your video is attempting to transcode and tone map the video, but is unable to.
What are the server's hardware specs? And what OS is it running?
RE: 4k HEVC Playback Issues in Browser - tbrewst - 2024-09-05
Alright - So apologies because I'm pretty fresh when it comes to this so let me know if you need something else
I've got my media stored on a Synology D423+ with internal Intel Celeron CPU
- DSM 7.2.1
- 18gb of physical memory
- I did set up hardware acceleration when I installed the Jellyfin in container
Here's the YAML config:
services:
jellyfin:
#for specific image-> image: jellyfin/jellyfin:10.8.13
image: jellyfin/jellyfin:10.9.9
container_name: Jellyfin
environment:
#- PUID=0
#- PGID=0
- TZ=America/Los_Angeles
#- JELLYFIN_PublishedServerUrl=192.168.1.#
#note: change TZ to your timezone identifier: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
volumes:
- /volume1/docker/jellyfin/cache
cache:rw- /volume1/docker/jellyfin/config
config:rw- /volume1/movies/
movies:ro- /volume1/tv
tv:ro- /volume1/music
music:ro#note: (:rw = read/write) & (:ro = read only)
devices:
- /dev/dri/renderD128
dev/dri/renderD128- /dev/dri/card0
dev/dri/card0#note: uncomment these lines in devices to allow for HWA to work on Synology units with an iGPU
ports:
- 8096:8096/tcp
#- <port-to-use>:8096/tcp
network_mode: bridge
#network_mode: host
restart: unless-stopped
RE: 4k HEVC Playback Issues in Browser - TheDreadPirate - 2024-09-05
Tone mapping is not possible on Synology NASes. Not because of the hardware, but because of the old Linux kernel most of their models still use. Intel's OpenCL driver deprecated support for Linux kernel 4.4 last year. And kernel 4.4.X is the version most Synology NASes still use.
You can disable tone mapping, but the resulting transcode will be washed out.
RE: 4k HEVC Playback Issues in Browser - tbrewst - 2024-09-05
So that was an early issue that I had where I figured out that the tone mapping was causing stuff to not play when it was turned on.
So I've got it toggled on right now and it works - as in I can see the wash out difference when it's on vs off.
Is my hardware that's "working" just doing the tone mapping itself?
RE: 4k HEVC Playback Issues in Browser - TheDreadPirate - 2024-09-05
Tone mapping is the process of converting the source video's color space to another color space. In this case HDR (probably BT2020) to SDR (BT709).
The clients that are working are either tone mapping locally (Intel MAC?) or just displaying the HDR video unmodified (phone and LG TV?).
RE: 4k HEVC Playback Issues in Browser - tbrewst - 2024-09-05
I did a test with the 4k resto of Casablanca and Blade Runner 2049 and the picture was noticeably washed in comparison to the literal disc source when tone mapping was toggled off in Jellyfin.
When I turned it on after I set up hardware transcode, the color profiles on JF matched the disc source after setting up hardware transcoding as well.
But yes - only on the intel mac/LG/iPhone. Oddly (or maybe not oddly) the iPhone was matching the source in terms of color as best as I could compare a phone to an Oled 4k TV.
Even toggling between different tone mapping profiles, i.e. BT.2390 and Mobius, I was seeing a difference in color - leading me to believe that SOMETHING was mapping tone.