Search the Community

Hi, I have hosted emby as docker on my unraid server for an extended period of time. Recently I have upgraded a nvidia RTX 4060 LP card for my server. I followed online instructions to install nvidia-driver, enable runtime parameter in docker, add NVIDIA_DEVICE and CAPABILITIES. Then I tried with handbrake docker to transcode H264 files to H265 with this GPU, and it worked just fine. So I think the path from physical GPU card to being utilized by docker is working. Then when I setup emby hw transcoding, there are a few issues that essentially preventing the full GPU power to be utilized. I enabled hw transcoding, stream a high quality film through local network using edge browser. At first the transcoding is doing fine, the server shows normal usage of decoder and encoder. But as I drag the bar to a later time, the playback pretty much stops. The decoder usage becomes 100% while encoder down to 0%. In the emby console page, the red playback progress bar becomes unsync with green transcode progress bar. If I jump to a later time but with a few play/pause click, there is a chance playback bar would sync with transcode bar, and the transcoded stream continues. However, the transcode may become very unstable. After I jump to different time point for serveral times, the transcode just stops, and stream just shows black display. I tried another *.wmv(VC1) file just to test if anything with the decoder/encoder compatibility issues. If I set transcode to be done by sw, it works fine. If I set transcode to be done by hw, the playback is similiar to the situation above but worse. I am not quite sure what kind of screenshots and logs that may help with the diagnostic. Just let me know and I will reply ASAP. Thanks in advance!

So, a few months ago, for whatever reason, I disabled hardware transcoding. I was running into bottlenecks with TDARR and Emby both trying to use the GPU for transcoding and it not being able to keep up. So, in my infinite wisdom decided to keep TDARR with the GPU, and Emby on the CPU. (I know... dumb...) But for the last few weeks I've been trying to switch it the other way around, and now Emby refuses to work with hardware. I keep getting the "No compatible streams are available" error. When I disabled it, I don't think I changed anything in the Unraid docker config. I just disabled it in the transcode settings in Emby itself. I've attached logs. I've tried two different versions of the drivers. As well as the official docker, and binhex. Both with the same results. IDFK what else to do... Any help would be greatly appreciated. embyserver.txt ffmpeg-transcode-5941a232-18d4-4b0c-863a-84dd71b5a166_1.txt ffmpeg-transcode-caaad69e-9807-445c-abb4-21dd27bc0e89_1.txt hardware_detection-63864919519.txt ffmpeg-transcode-f434a280-9fcb-4692-ac03-109b2c0fe87d_1.txt ffmpeg-transcode-fbc7aefb-0f66-4b5a-b74b-70eca438b182_1.txt

Hello, 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 ?

I have a QNAP TS-453Pro (w/16GB RAM) and recently started looking at Emby as an alternative to Plex. I like that Emby has support for HW transcoding, but it currently appears that it does NOT support QNAP's implementation of it - CodexPack. Are there any plans to build in support for CodexPack, or an option to allow users to repoint to "vendor-specific" files (ffmpeg, etc.)? The CPU utilization w/o the HW Transcoding support is pretty high. Thanks, T.