2015-09-02, 13:05
Progressive content in interlaced container (progressive segmented frames, i.e. 25p stored in interlaced fields) is not recognized in Windows Kodi builds while on Android Kodi it is.
Windows Kodi (DX9/DX11) erroneously applies deinterlacing when deinterlacing is set to Auto (i.e. 25 fps -> 50 fps according to the debug overlay). Android Kodi using the same Auto deinterlacing setting keeps it at 25 fps like it should.
The material in question originates from a Canon HF100 camcorder and MediaInfo, among others, incorrectly reports it as interlaced so admittedly it is tricky.
Just wondering if anyone knows what's making it work on Android and if anything could be done in the Windows Kodi code to solve it?
My Android device is unrooted Galaxy Note 4 and HTPC is Win 10 64bit, Intel HD 3500 graphics, graphics settings mostly on auto, DXVA2 enabled.
Windows Kodi (DX9/DX11) erroneously applies deinterlacing when deinterlacing is set to Auto (i.e. 25 fps -> 50 fps according to the debug overlay). Android Kodi using the same Auto deinterlacing setting keeps it at 25 fps like it should.
The material in question originates from a Canon HF100 camcorder and MediaInfo, among others, incorrectly reports it as interlaced so admittedly it is tricky.
Just wondering if anyone knows what's making it work on Android and if anything could be done in the Windows Kodi code to solve it?
My Android device is unrooted Galaxy Note 4 and HTPC is Win 10 64bit, Intel HD 3500 graphics, graphics settings mostly on auto, DXVA2 enabled.
