home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MP 1.3.x dshowhelper development
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="DragonQ" data-source="post: 986720" data-attributes="member: 115209"><p>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.</p><p> </p><p></p><p>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.</p><p> </p><p>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 <em>before</em> resizing or applying post-processing effects, and the only way to do <em>hardware</em> 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.</p><p> </p><p>Currently MediaPortal's scaling algorithm in EVR is poor, so ffdshow resizing is necessary for good quality SD video (IMO).</p></blockquote><p></p>
[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]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MP 1.3.x dshowhelper development
Contact us
RSS
Top
Bottom