QNAP TS-664 Docker, Hardware transcoding not working

shadowempire · March 7, 2024, 12:56pm

Server Version#: 1.40.0.7998
Player Version#: Web/iPhone

I followed:
https://support.plex.tv/articles/115002178853-using-hardware-accelerated-streaming

Mar 07, 2024 13:43:26.269 [139698033597240] Debug — [Req#3a66/Transcode] Codecs: testing h264 (decoder) with hwdevice vaapi
Mar 07, 2024 13:43:26.269 [139698033597240] Debug — [Req#3a66/Transcode] Codecs: hardware transcoding: testing API vaapi for device ‘/dev/dri/renderD128’ (JasperLake [UHD Graphics])
Mar 07, 2024 13:43:26.269 [139698033597240] Error — [Req#3a66/Transcode] [FFMPEG] - No VA display found for device /dev/dri/renderD128.
Mar 07, 2024 13:43:26.269 [139698033597240] Debug — [Req#3a66/Transcode] Codecs: hardware transcoding: opening hw device failed - probably not supported by this system, error: Invalid argument
Mar 07, 2024 13:43:26.269 [139698033597240] Debug — [Req#3a66/Transcode] Could not create hardware context for h264
Mar 07, 2024 13:43:26.270 [139698033597240] Debug — [Req#3a66/Transcode] MDE: Selected protocol hls; container: mp4
Mar 07, 2024 13:43:26.270 [139698033597240] Debug — [Req#3a66/Transcode] MDE: analyzing media item 6300
Mar 07, 2024 13:43:26.270 [139698033597240] Debug — [Req#3a66/Transcode] MDE: Star Wars: Episode V - The Empire Strikes Back (1980): no direct play video profile exists for http/mkv/h264
Mar 07, 2024 13:43:26.270 [139698033597240] Debug — [Req#3a66/Transcode] MDE: Star Wars: Episode V - The Empire Strikes Back (1980): no direct play video profile exists for http/mkv/h264/dca
Mar 07, 2024 13:43:26.270 [139698033597240] Debug — [Req#3a66/Transcode] Star Wars: Episode V - The Empire Strikes Back - audio.channels limitation applies: 7 > 6
Mar 07, 2024 13:43:26.270 [139698033597240] Debug — [Req#3a66/Transcode] MDE: Star Wars: Episode V - The Empire Strikes Back (1980): selected subtitle cannot be converted to a compatible format, burning into video stream
Mar 07, 2024 13:43:26.270 [139698033597240] Debug — [Req#3a66/Transcode] MDE: Star Wars: Episode V - The Empire Strikes Back (1980): avoiding video remux due to burned subtitle stream
Mar 07, 2024 13:43:26.270 [139698033597240] Debug — [Req#3a66/Transcode] MDE: Star Wars: Episode V - The Empire Strikes Back (1980): no remuxable profile found, so video stream will be transcoded
Mar 07, 2024 13:43:26.270 [139698033597240] Debug — [Req#3a66/Transcode] MDE: Cannot direct stream video stream due to profile or setting limitations
Mar 07, 2024 13:43:26.270 [139698033597240] Debug — [Req#3a66/Transcode] Codecs: testing h264 (decoder) with hwdevice vaapi
Mar 07, 2024 13:43:26.271 [139698033597240] Debug — [Req#3a66/Transcode] Codecs: hardware transcoding: testing API vaapi for device ‘/dev/dri/renderD128’ (JasperLake [UHD Graphics])
Mar 07, 2024 13:43:26.271 [139698033597240] Error — [Req#3a66/Transcode] [FFMPEG] - No VA display found for device /dev/dri/renderD128.

Running Plex in a container:

plex:

container_name: plex

image: plexinc/pms-docker:public

restart: unless-stopped

logging:

driver: json-file

environment:

- PUID=$PUID

- PGID=$PGID

- TZ=$TZ

- UMASK=002

- DEBUG=no

- PLEX_CLAIM=$PLEX_CLAIM

- PLEX_PASS=$PLEX_PASS

- ADVERTISE_IP=$PLEX_ADVERTISE_IP

volumes:

- /etc/localtime:/etc/localtime:ro

- ./plex:/config:rw

- ./plex:/transcode:rw

- /share/2watch/tv:/media/tv:rw

devices:

- /dev/dri:/dev/dri

network_mode: host

My CPU supports JasperLake (Intel Celeron® N5095).

Please help…
thx
br Jörg

seems related to:

github.com/linuxserver/docker-plex

Incorrect permissions for /dev/dri

opened 03:45AM - 17 Sep 19 UTC

closed 11:49AM - 19 Sep 19 UTC

kevindd992002

[linuxserverurl]: https://linuxserver.io [![linuxserver.io](https://raw.githubu…sercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver_medium.png)][linuxserverurl] ## Thanks, team linuxserver.io In your docuemntation, it says: > Hardware acceleration users for Intel Quicksync will need to mount their /dev/dri video device inside of the container by passing the following command when running or creating the container: > > --device=/dev/dri:/dev/dri > > We will automatically ensure the abc user inside of the container has the proper permissions to access this device. I'm running docker-compose with Debian 10/Linux Kernel 5.2 (Buster Backports). I have my docker-compose.yml file set like so: ``` plex: image: linuxserver/plex container_name: plex network_mode: host volumes: - /home/kevin/appdata/plex:/config - /mnt/storage/shows:/data/tvshows - /mnt/storage/movies:/data/movies restart: unless-stopped devices: - /dev/dri:/dev/dri environment: - PUID=${PUID} - PGID=${PGID} - TZ=Asia/Manila - VERSION=latest ``` Output of `ls -la /dev/dri` in my host machine is: ``` root@epsilon:~# ls -la /dev/dri total 0 drwxr-xr-x 3 root root 100 Sep 16 00:04 . drwxr-xr-x 17 root root 3520 Sep 16 00:04 .. drwxr-xr-x 2 root root 80 Sep 16 00:04 by-path crw-rw---- 1 root video 226, 0 Sep 16 00:04 card0 crw-rw---- 1 root render 226, 128 Sep 16 00:04 renderD128 ``` Output of `ls -la /dev/dri` inside the plex container is: ``` root@epsilon:/# ls -la /dev/dri total 0 drwxr-xr-x 2 root root 80 Sep 16 00:04 . drwxr-xr-x 6 root root 360 Sep 16 00:04 .. crw-rw---- 1 root video 226, 0 Sep 16 00:04 card0 crw-rw---- 1 root 105 226, 128 Sep 16 00:04 renderD128 ``` This clearly is an issue because the container does not have the `render` group which means that the abc user does not have access to the `renderD128` device. This breaks HW transcoding. As a workaround, I can `chown` renderD128 so that it is owned by the PUID I specified. This is not an ideal solution because upon restart the permissions of those devices get reset and we shouldn't do this extra step anyway if the container is working correctly. Changing device permissions is not good practice at all. @aptalca is already aware of this issue as I mentioned it in the Discord channel. I hope you guys can take a look at this and acknowledge it as a real issue. Thank you very much for your continued support and great work for the community!

after setting permissions, it worked

github.com/linuxserver/docker-jellyfin

Hardware acceleration isn't working properly

opened 07:15PM - 30 Mar 20 UTC

closed 09:26PM - 29 Jun 22 UTC

fengapappit

no-issue-activity

## Expected Behavior Enabling VAAPI hardware acceleration in Jellyfin should wo…rk in its default configuration. ## Current Behavior First issue is with the default transcode directory. As it does not exist and Jellyfin doesn't create it, it's impossible to use the default configuration. Secondly, once the devices are setup according to my host, the default user is not able to access them. Any transcode attempt leads to the following error message: ``` /usr/lib/jellyfin-ffmpeg/ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -vaapi_device /dev/dri/renderD128 -i file:"/jellyfin/media/12 Angry Men (1957)/12 Angry Men (1957) Bluray-1080p.mkv" -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 h264_vaapi -b:v 10201576 -maxrate 10201576 -bufsize 20403152 -profile:v high -level 41 -force_key_frames:0 "expr:gte(t,0+n_forced*3)" -vf "format=nv12|vaapi,hwupload,scale_vaapi=format=nv12" -copyts -vsync -1 -codec:a:0 aac -strict experimental -ac 1 -ab 192000 -f hls -max_delay 5000000 -avoid_negative_ts disabled -start_at_zero -hls_time 3 -individual_header_trailer 0 -hls_segment_type mpegts -start_number 0 -hls_segment_filename "/config/cache/temp/69e65dd7670476af5b32268cf32dcb6f%d.ts" -hls_playlist_type vod -hls_list_size 0 -y "/config/cache/temp/69e65dd7670476af5b32268cf32dcb6f.m3u8" ffmpeg version 4.2.1 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1) configuration: --toolchain=hardened --prefix=/usr --target-os=linux --enable-cross-compile --extra-cflags=--static --enable-gpl --enable-static --disable-doc --disable-ffplay --disable-shared --disable-libxcb --disable-sdl2 --disable-xlib --enable-libfontconfig --enable-fontconfig --enable-gmp --enable-gnutls --enable-libass --enable-libbluray --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libwebp --enable-libx264 --enable-libx265 --enable-libzvbi --enable-omx --enable-omx-rpi --enable-version3 --enable-vaapi --enable-vdpau --arch=amd64 --enable-nvenc --enable-nvdec --enable-amf libavutil 56. 31.100 / 56. 31.100 libavcodec 58. 54.100 / 58. 54.100 libavformat 58. 29.100 / 58. 29.100 libavdevice 58. 8.100 / 58. 8.100 libavfilter 7. 57.100 / 7. 57.100 libswscale 5. 5.100 / 5. 5.100 libswresample 3. 5.100 / 3. 5.100 libpostproc 55. 5.100 / 55. 5.100 [AVHWDeviceContext @ 0x563fc93af5c0] No VA display found for device /dev/dri/renderD128. Device creation failed: -22. Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Invalid argument Error parsing global options: Invalid argument ``` When running the same exact command through a root shell to the docker, it works as expected and transcoding works. I've tried adding the abc user to the video group, doesn't change anything. Same thing for running the docker container as high privilege. I wanted to try running the service as root but I can't find what is starting the service nor where I can configure this. I got lost in /etc/s6 as I'm completely unfamiliar with it. ## Steps to Reproduce 1. Enable VAAPI transcoding in Playback options and save the settings 2. Notice that it gives an error concerning the transcode directory 3. Re-enable VAAPI and change the directory to something existing, such as /config/cache/temp/ and save the settings 4. Try playing anything needing transcode ## Environment **OS:** Synology DSM 6.2.2-24922 Update 4 **CPU architecture:** INTEL Celeron J3455 **How docker service was installed:** Docker was installed through Synology store. Same for the image. Since it does not support custom configuration, especially the devices, I had to import the following configuration file to make it work: ``` { "cap_add" : null, "cap_drop" : null, "cmd" : "", "cpu_priority" : 50, "devices" : [ { "CgroupPermissions": "rwm", "PathInContainer": "/dev/dri/renderD128", "PathOnHost": "/dev/dri/renderD128" }, { "CgroupPermissions": "rwm", "PathInContainer": "/dev/dri/card0", "PathOnHost": "/dev/dri/card0" } ], "enable_publish_all_ports" : false, "enable_restart_policy" : false, "enabled" : false, "entrypoint_default" : "/init", "env_variables" : [ { "key" : "PATH", "value" : "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" }, { "key" : "HOME", "value" : "/root" }, { "key" : "LANGUAGE", "value" : "en_US.UTF-8" }, { "key" : "LANG", "value" : "en_US.UTF-8" }, { "key" : "TERM", "value" : "xterm" }, { "key" : "NVIDIA_DRIVER_CAPABILITIES", "value" : "compute,video,utility" }, { "key" : "PGID", "value" : "101" }, { "key" : "PUID", "value" : "1026" } ], "exporting" : false, "id" : "851b673d1b03caae27ad79561568172a9b7b8525bd01687582b85927686deef3", "image" : "linuxserver/jellyfin:latest", "is_ddsm" : false, "is_package" : false, "links" : [], "memory_limit" : 0, "name" : "linuxserver-jellyfin-latest", "network" : [ { "driver" : "bridge", "name" : "bridge" } ], "network_mode" : "bridge", "port_bindings" : [ { "container_port" : 8096, "host_port" : 0, "type" : "tcp" }, { "container_port" : 8920, "host_port" : 0, "type" : "tcp" } ], "privileged" : false, "shortcut" : { "enable_shortcut" : false }, "use_host_network" : false, "volume_bindings" : [ { "host_volume_file" : "/test", "mount_point" : "/jellyfin/media", "type" : "rw" } ] } ``` ## Command used to create docker container (run/create/compose/screenshot) ![image](https://user-images.githubusercontent.com/6908355/77951423-55671280-72ca-11ea-80a5-08a05cc6f1ae.png) The previously mentioned configuration pretty much maps to a docker compose command. I'd be glad if you could provide a tip in changing the user running the Jellyfin service from abc to root as a quick fix, as everything I've tried didn't work.

howto fix this permanently?

shadowempire · March 7, 2024, 1:42pm

Add the user to the group “render” fixes the problem.
Would be nice to have this documented in the guide…

system · June 5, 2024, 1:42pm

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Hardware transcoding not working in docker Plex Media Server server-linux , server-docker	37	762	April 6, 2023
Help enable Hardware Transcoding on QNAP 453Be - Not working! NAS & Devices server-docker	13	2846	May 4, 2020
Hardware Transcoding issue (quicksync) in docker NAS & Devices server-linux , server-synology	25	430	September 27, 2023
Hardware transcoding on Qnap TVS-672XT NAS & Devices server-qnap	85	3110	January 5, 2021
Hardware transcoding stopped working on Synology NAS NAS & Devices server-synology	10	1171	August 8, 2021

QNAP TS-664 Docker, Hardware transcoding not working

Related topics