** Message: 00:03:52.688: udev: Failed to lookup device /dev/sda Libva info: Found init function _vaDriverInit_1_13 Libva info: Trying to open /app/extensions/IntelMediaSDK/lib/dri/iHD_drv_video.so Libva info: User environment variable requested driver 'iHD' hb_display_init: attempting VA driver 'iHD' Compile-time hardening features are enabled 1.4.2-x86_64.flatpak Where did you download HandBrake from? Ubuntu Desktop 21.10 What version of HandBrake are you running? VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP VAProfileHEVCMain444_10 : VAEntrypointVLD VAProfileHEVCMain444 : VAEntrypointEncSliceLP VAProfileHEVCMain422_10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSliceLP VAProfileHEVCMain : VAEntrypointEncSliceLP VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointEncSliceLP Vainfo: Supported profile and entrypoints Vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 21.3.3 () Handbrake does do that which I think is stupid.Vainfo: VA-API version: 1.12 (libva 2.10.0) If you look at the command it runs it'll use `hevc_vaapi` instead of `hevc_qsv` which will provide better results.Ĭhecking if it's working, if you've grabbed a 'QSV' plugin (which 99% of them use VAAPI) it would just error out and not silently fall back to CPU, unless you're doing Handbrake. I won't go into detail about CPU vs GPU and different encoders, but you're actually using the worst one available to QSV, which is VAAPI. This is important and counter intuitive: Set the hardware encoding type to vaapi and not qsv. Same reason why the usage shows up in the GPU section of Unraid. In 2.00.12 (latest release) there was a pretty significant update regarding drivers, so that's indeed not necessary anymore. On the node after the container starts up If you see the opposite, your CPU is taking the load and not QSV Your 3D Render and Video Load should be high while your CPU is overall load is low. Install GPU Statistics and Intel GPU TOP Plugins from the Community Applications. On my system: 1 GPU Transcode and 2 GPU Health Checks ![]() This is important and counter intuitive: Set GPU instances not CPU! Your CPU's QSV engine is considered a GPU to Tdarr. I will not comment on the number of Transcode and Health Check instances which give you the best performance since everyones system is slightly different and I haven't done any extensive testing of my own. Go to Tdarr Dashboard, click on your Node to expand the Node view. Set QSV to true, keep NVEC to false, set your subtitle preferences. Disable the default Tdarr_Plugin_MC93_Migz1FFMPEG. In the Plugin Stack, bring up DrDD H265 MKV AC3 audio subtitles to the second postion after Tdarr_Plugin_lmg1_Reorder_Streams. Paste ID in your library Transcoding Options (repeat for TV Shows and Movies) Go to Plugins, QSV H265, I have personally selected DrDD H265 MKV AC3 audio subtitles In Tdarr GUI, create your two libraries: TV Shows and Movies Let me know if you have a different outcome and I'll edit the post. I did not find this step was required when writting this post. Go to node's console and run the following:Īpt-get install intel-media-va-driver-non-free Note - I have seen this step on different reddit posts: On the node after the container starts up On tdar_node set Extra Parameters to -device=/dev/dri ![]() ![]() Hopefuly this will save you chaps a few head aches.įollow this guide to get Plex to work with QSV hardware transcoding.įollow SpaceInvader One's Youtube tutorial on how to install tdarr and tdarr_node: Like many of you, this ended up being a lot of trial and error of things I found across different parts of reddit to get to work. Here is a step by step guide on how I managed to get QSV transcoding working in Tdarr on Unraid.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |