Win DXVA deinterlacing in Leia 18.2 not deinterlacing native interlaced content?
#1
Just fired up a Windows 10 install on an m3-6Y30 Intel Compute Stick with Leia 18.2 installed.

Live/Recorded TV and files (DVDs, transport streams, Blu-ray folders etc.) with native interlaced content aren't being deinterlaced with DXVA deinterlacing and DXVA2 hardware acceleration enabled.  Native interlaced i25 (1080i25 and 576i25 - aka 1080/50i and 576/50i) content is being weaved and is covered in combing, no bob, motion adaptive or motion compensative deinterlacing is being applied, so no 50Hz motion.

If I disable DXVA2 hardware acceleration in player settings and thus move to CPU-decode and CPU-deinterlace then I get decent YADIF 2x deinterlacing (and proper i25->p50 with no combing and 50Hz motion) and software h.264 or MPEG2 decoding.

How long has DXVA2 been borked with interlaced content - or is this something in configuration terms I've missed?
Reply
#2
Tried now on a Win 10 Pro x64, Kodi 18.2 x64.

With render method Auto Detect or DXVA deinterlacing is working fine (DXVA2 hardware decoding enabled), no combing seen. With render method Pixel shaders or Software (DXVA2 hardware decoding appears to not make a difference), instead, I get combing.

If one presses O to get player stats... deinterlace method is always indicated as "unknowr" (spelling mistake included). I've been lamenting the opacity of Windows video playback options for the longest of times... I don't know who I should point out stuff to or where to point it out. Sad
For troubleshooting and bug reporting please make sure you read this first.
Reply
#3
OK - found out my issue.

Render method in Player settings was blank - so I guess in AUTO mode? If I force it to DXVA Render and enable DXVA2 acceleration then all is good and I get full acceleration.

I guess either a previous install set the Render method incorrectly - or the default isn't always ideal?
Reply
#4
(2019-04-28, 16:46)noggin Wrote: I guess either a previous install set the Render method incorrectly - or the default isn't always ideal?
Yeah... you see? The point is there's no way to understand how all the options interact.
If I look at the wiki, here: https://kodi.wiki/view/Settings/Player/V...Processing

How can I tell what happens when I set the render method to Auto? What happens with DXVA, what with Pixel shaders, what with Software? Do HQ scalers work for all render methods? Apparently HQ scalers for DXVA were introduced for Kodi Gotham, several years ago. But then why software *and* pixel shaders still exist? What is the difference between them? What their purpose?
How can one know what deinterlacing method is used if playback info always reports "unknown"?
For troubleshooting and bug reporting please make sure you read this first.
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
DXVA deinterlacing in Leia 18.2 not deinterlacing native interlaced content?00