Professional Documents
Culture Documents
Normally your processor (CPU) does all the work when decoding video. When using hardware acceleration, most of
that work is moved to the graphics processor (GPU). This significantly reduces the usage of CPU resources, which
can be particularly useful if you have a relatively slow CPU. Most graphics chips have dedicated circuitry for decoding
video and thus can do it very efficiently.
Our recommendation is to use it only when really needed. That means use it only if you have a slow computer that
has very high CPU usage when playing videos without acceleration.
Hardware acceleration can also be useful on laptops and tablets, because it can help reduce power consumption and
thus increase battery life.
Hardware acceleration only helps to reduce CPU usage. It has no effect on video quality.
Usage of hardware acceleration increases the chance of playback problems. Usually caused by graphics driver bugs.
So if you decide to use hardware acceleration, it is important to use up-to-date drivers.
DXVA2 native
DXVA2 copy-back
NVIDIA CUVID
Intel QuickSync
DXVA is a generic interface for hardware acceleration that was created by Microsoft. It works with all brands of
GPUs.
CUVID is an interface created by NVIDIA and it only works with GPUs from NVIDIA.
QuickSync is an interface created by Intel and is supported only by the integrated GPUs of Intel Core processors
(Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Kaby lake, and newer).
QuickSync and CUVID work similarly as DXVA2 copy-back. This means that the decoded video is copied back from
GPU memory to CPU memory. This allows the video to undergo additional processing after it has been decoded.
They basically act the same as a normal (software) decoder.
It is strongly recommend to use DXVA instead of QuickSync or CUVID, even if you have an Intel or NVIDIA GPU.
DXVA is more reliable and efficient.
A disadvantage of CUVID is that it forces the GPU into high performance mode, which increases its power
consumption.
In case of QuickSync it is important to download the graphics driver from the Intel website, because the drivers that
are distributed through Windows Update may not include all required QuickSync components.
DXVA implementations come in two variants: native and copy-back. The difference is explained below.
The LAV video decoder that is included in the codec pack offers both variants.
The compressed video is send to your graphics processor (GPU) where it gets decoded. In case of the native mode,
the decoded video stays in GPU memory until it has been displayed. In case of the copy-back mode, the video is
copied to your normal memory. This allows additional processing to be done in the playback chain. Once done, the
video is copied back to GPU memory again for displaying.
Copy-back mode is a bit less efficient because of those two copy operations, which means a bit more work must be
done by both the GPU and the CPU. It does however provide the same freedom as normal software decoding.
Native mode has some limitations because the decoded video stays in GPU memory (where the player can't access
it). The most important limitation is that the video decoder must be connected directly to the video renderer in the
playback chain. There can't be any processing filters in between.
Processing filters are only needed in specific situations. For example if you use Windows Media Player, then you
need VSFilter for displaying subtitles. So in case of WMP you should use copyback mode. MPC-HC (which is our
recommended player) has an internal subtitles renderer that is also compatible with DXVA in native mode.
Old AMD/ATI and Intel chips from before 2010 do not have good performance when copying data from GPU to CPU
memory. Copy-back may not give smooth playback on such old systems, so we recommend to use native mode
instead.
Why does the installer show less options than mentioned in this help?
Here are some rules of thumb to help you decide which option to choose. They are listed in order or importance.
NVIDIA CUVID, Intel QuickSync, and DXVA copy-back all have no special requirements with regards to subtitles.
They act similar to normal software decoders.
Native implementations of DXVA have the limitation that they need to be connected directly to the video renderer.
This means that it is not possible to use a subtitle filter such as DirectVobSub (a.k.a. VSFilter).
The only proper way to get subtitle functionality in combination with DXVA native is to use an advanced player with
an internal subtitle renderer, that also uses a video renderer that supports combining subtitles with DXVA input.
MPC-HC, which is included in the Standard/Full/mega versions of the K-Lite codec pack, has that capability.
Examples of other players with similar capabilities are: ZoomPlayer, PotPlayer, GOM Player, and KMPlayer.
Windows Media Player and Media Center do NOT support subtitles in combination with DXVA native. You either
need to use a different player, or a different hardware acceleration method, such as DXVA2 copy-back.
If you have a slow and inefficient CPU and a low-end GPU, then it might give a small reduction in power
consumption. Laptops often have a low-end GPU.
If you have a fast CPU or a high-end GPU, then power usage might actually be higher with hardware acceleration
enabled. The difference is usually pretty small.
NVIDIA cards can go in high performance mode when using CUVID hardware acceleration. A tool called NVIDIA
Inspector can be used to tweak this behavior and reduce power consumption.
MPEG-2 is a relatively simple format to decode, so hardware acceleration is typically not necessary for this format.
In case of H.264 only 8-bit video can be decoded by hardware. In case of HEVC and VP9 there is also support for
decoding 10-bit video on some GPUs.
Hardware acceleration of HEVC and VP9 is only supported by a limited number of GPUs.
Problems with hardware accelerated video decoding are often driver related. So the first thing you should try is to
update your graphics driver. You should download the driver directly from the website of the manufacturer of the
graphics chip (AMD, NVIDIA, or Intel). Do not get drivers from WindowsUpdate, because those driver are usually
older and often do not contain all components required for hardware acceleration (in case of CUVID and QuickSync).
You should also switch to normal software decoding to confirm if the problem is related to hardware acceleration.