If you are using Intel or AMD, you will see QSV or VCE respectively.Ħ. Since I’m using Nvidia, I’m selecting the “H.264 Nvidia NVENC” codec. Here, select the hardware decoder from the “ Video Codec” drop-down menu.
To do that, add a video file to HandBrake and go to the “ Video” tab. After enabling GPU support, you need to select the video codec. If the encoder options are greyed out, it means that your GPU doesn’t support hardware encoders.Ĥ. In my case, since I have Nvidia GPU with NvEnc, I selected the “Allow use of the Nvidia NVENC Encoders” option. HandBrake automatically detects your GPU hardware encoders. On the right-panel, select the Encoder of your choice. In the Preferences window, go to the “ Video” tab. You can also open the same from “Tools → Preferences”.ģ.
After opening HandBrake, click on the “ Preferences” link appearing on the bottom left corner. First, open HandBrake by searching for it in the start menu.Ģ. If you are interested, take a look at this support document that goes into great detail with various tests. When you force HandBrake to use GPU encoding, it comes at the expense of lower quality and higher file size compared to the CPU encoding.If your GPU has no hardware encoders, you cannot use HandBrake with the GPU.Generally, you can find if your graphics card supports these hardware encoders by looking at the spec sheet available on the manufacturer’s website. Specifically, VCE for AMD graphics cards, NVENC for Nvidia, and QSV for Intel. Your graphics card should have built-in hardware encoders.Things to Know Before Forcing GPU Transcodeīefore you can go ahead and enable GPU support in Handbrake, there are few things you need to know. So, without further ado, let me show you the steps to enable GPU support in HandBrake. One of the biggest benefits of using GPU transcoding is that it takes less time compared to CPU transcoding, at least in my case. The good thing is, if you have a dGPU (Dedicated Graphics Processing Unit), you can force HandBrake to use that GPU instead of relying solely on the CPU resources.
0 kommentar(er)
