![]() |
HW transcoding on Synology failed - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: HW transcoding on Synology failed (/t-hw-transcoding-on-synology-failed) |
HW transcoding on Synology failed - lilies1 - 2025-03-11 Hi there, I’m using Jellyfin (Version 10.8.11) on a Synology DS224+ (latest DSM) in a docker container. Most of my videos are in 1024i H264 format - however I’m not able to hardware transcode this specific format. The error will be always that the client is not compatible with the video format. I already tried to switch to the latest Jellyfin version - no change. Other formats are working fine with HW transcoding. Are there any restrictions on interlaced video formats/codecs? What needs to be done to get it work? Attached the error dump and the section for HW decoding in the compose file. Thanks for ideas… Andreas Log: ffmpeg version 5.1.3-Jellyfin Copyright © 2000-2022 the FFmpeg developers built with gcc 10 (Debian 10.2.1-6) configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-libs=-lfftw3f --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-libdrm --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=amd64 --enable-libsvtav1 --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-opencl --enable-vaapi --enable-amf --enable-libmfx --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc libavutil 57. 28.100 / 57. 28.100 libavcodec 59. 37.100 / 59. 37.100 libavformat 59. 27.100 / 59. 27.100 libavdevice 59. 7.100 / 59. 7.100 libavfilter 8. 44.100 / 8. 44.100 libswscale 6. 7.100 / 6. 7.100 libswresample 4. 7.100 / 4. 7.100 libpostproc 56. 6.100 / 56. 6.100 [AVHWDeviceContext @ 0x5638ee97ba00] No VA display found for any default device. Device creation failed: -22. Failed to set value 'vaapi=va:,driver=iHD,kernel_driver=i915' for option 'init_hw_device': Invalid argument Error parsing global options: Invalid argument Compose file: … devices: - /dev/dri/renderD128:/dev/dri/renderD128 - /dev/dri/card0:/dev/dri/card0 … RE: HW transcoding on Synology failed - Efficient_Good_5784 - 2025-03-11 Can you share how your transcoding settings look like within Jellyfin's dashboard? RE: HW transcoding on Synology failed - TheDreadPirate - 2025-03-11 Try passing in just "/dev/dri" into the container. The Intel driver will figure out the rest. And can you share the full ffmpeg log? RE: HW transcoding on Synology failed - lilies1 - 2025-03-11 (2025-03-11, 08:45 PM)Efficient_Good_5784 Wrote: Can you share how your transcoding settings look like within Jellyfin's dashboard? Here we go...hope you don't mind that settings are in German.... RE: HW transcoding on Synology failed - lilies1 - 2025-03-11 (2025-03-11, 08:47 PM)TheDreadPirate Wrote: Try passing in just "/dev/dri" into the container. The Intel driver will figure out the rest. Versus what I put in today...how should the statement look like? What's your suggestion? devices: - /dev/dri/renderD128:/dev/dri/renderD128 - /dev/dri/card0:/dev/dri/card0 Down below you'll find the full error message. As I switched to Jellyfin 10.10.6 meanwhile, the error message looks a bit different now. ![]() RE: HW transcoding on Synology failed - TheDreadPirate - 2025-03-12 Code: /dev/dri:/dev/dri |