Reply to thread

Message

When you use DXVA2 Native, the best deinterlacing algorithm is chosen automatically when using an nVidia GPU. So you'll get the same results when using DXVA2 Native as you would when using CUVID with "Enable Adaptive HW Deinterlacing", "50p/60p (Video)" and "High-Quality Processing" all ticked in LAV Video Configuration.

The result is the same, except that DXVA2 Native uses less power and is a bit less flexible when it comes to what content it can handle.

For MediaPortal, I can only think of one reason to use CUVID, which is the reason I use it: when doing post-processing. Deinterlacing should always be done before resizing or applying post-processing effects, and the only way to do hardware deinterlacing before post-processing is to use CUVID with the options listed above enabled. This means that the image is decoded and deinterlaced using CUVID before ffdshow gets its hand on it for post-processing.

Currently MediaPortal's scaling algorithm in EVR is poor, so ffdshow resizing is necessary for good quality SD video (IMO).

<blockquote data-quote="DragonQ" data-source="post: 986720" data-attributes="member: 115209">When you use DXVA2 Native, the best deinterlacing algorithm is chosen automatically when using an nVidia GPU. So you'll get the same results when using DXVA2 Native as you would when using CUVID with &quot;Enable Adaptive HW Deinterlacing&quot;, &quot;50p/60p (Video)&quot; and &quot;High-Quality Processing&quot; all ticked in LAV Video Configuration.&nbsp;The result is the same, except that DXVA2 Native uses less power and is a bit less flexible when it comes to what content it can handle.&nbsp;For MediaPortal, I can only think of one reason to use CUVID, which is the reason I use it: when doing post-processing. Deinterlacing should always be done before resizing or applying post-processing effects, and the only way to do hardware deinterlacing before post-processing is to use CUVID with the options listed above enabled. This means that the image is decoded and deinterlaced using CUVID before ffdshow gets its hand on it for post-processing.&nbsp;Currently MediaPortal's scaling algorithm in EVR is poor, so ffdshow resizing is necessary for good quality SD video (IMO).</blockquote>

[QUOTE="DragonQ, post: 986720, member: 115209"] When you use DXVA2 Native, the best deinterlacing algorithm is chosen automatically when using an nVidia GPU. So you'll get the same results when using DXVA2 Native as you would when using CUVID with "Enable Adaptive HW Deinterlacing", "50p/60p (Video)" and "High-Quality Processing" all ticked in LAV Video Configuration. The result is the same, except that DXVA2 Native uses less power and is a bit less flexible when it comes to what content it can handle. For MediaPortal, I can only think of one reason to use CUVID, which is the reason I use it: when doing post-processing. Deinterlacing should always be done [i]before[/i] resizing or applying post-processing effects, and the only way to do [i]hardware[/i] deinterlacing before post-processing is to use CUVID with the options listed above enabled. This means that the image is decoded and deinterlaced using CUVID before ffdshow gets its hand on it for post-processing. Currently MediaPortal's scaling algorithm in EVR is poor, so ffdshow resizing is necessary for good quality SD video (IMO). [/QUOTE]