Search the Community
Showing results for tags 'hwaccel'.
NormSwarm posted a topic in LinuxHello, So, I'm using linuxserver/emby:beta for my docker image, I've passed the devices /dev/dri/card0 and /dev/dri/renderD128 to the container. Emby doesn't detect all the available profile for decoding and encoding (Also, I have an active Emby Premiere subscription). I've installed into the image `vainfo` into the container to check that everything is good and I see all the profile (like HEVC, H264): root@bd304a409b20:/# vainfo error: XDG_RUNTIME_DIR not set in the environment. error: can't connect to X server! libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.14 (libva 2.12.0) vainfo: Driver version: Mesa Gallium driver 22.0.5 for AMD Radeon Vega 3 Graphics (raven, LLVM 13.0.1, DRM 3.47, 5.19.17-Unraid) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc As you can see, there are more profile than just MPEG-2 and VP9, but those aren't found by emby. To test further, I've installed Jellyfin image. I've configured it to use hardware decoding using vaapi and selected the HEVC decoding (normal and 10 bit). I tested to stream to the browser a hevc 10bit file, it used hardware decoding without any issue. I check the GPU usage with radeontop. Here is a transcode log from jellyfin proving that ffmpeg had no issue using the device. transcode-log-jellyfin.log Emby hardware detection log: hardware_detection-63807243716.txt What can I do to force Emby to recognize the VAAPI profiles ?
@@Luke, as posted in https://emby.media/community/index.php?/topic/28528-how-can-you-tell-if-quicksync-is-working/?p=275763 , this is an important feature, even more now that more and more users have HW that can be used to accelerate encoding and decoding. Can this please be done now? I've recently bought new hardware and I'm not sure if my hw acceleration settings are actually working. Possibly no, because of the CPU usage I see.