Kodi Community Forum

Full Version: Hardware Deinterlacing not working on some Intel chips?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4
On my HTPC computer the hardware de-interlacing VAAPI is not working at all - a flying soccer ball looks more like a flying hedgehog Sad . When I inactivate hardware acceleration and do deinterlacing by software, the result is quite reasonable.

Also, with inactivated hardware-accel I get in the video settings of a running TV show the option:
1) Deinterlace Video: Active / Inactive / Auto
2) Deinterlace Method: Auto/ Software Blend /..../ Bob/...
3) Videoscaling Method: Auto/ Next Neighor/....
4) ...

With hardware-accel activated, the #2 is missing completely, everything else seems to be the same. And although #1 is set to Active, the video is not deinterlaced at all.

I use an MSI DC111 ( http://www.msi.com/product/desktop/Wind_...cification ) with Ubuntu 12.04, and xbmc 13.1 with tvheadend 3.9.xxx. Ubuntu reports the Processor and Graphics card as:
-- Processor: Intel® Celeron® CPU 1037U @ 1.80GHz × 2
-- Graphics: Intel® Ivybridge Mobile

On a separate Haswell computer (Processor: Intel® Core™ i7-4771 CPU @ 3.50GHz × 8; Graphic: Intel® Haswell Desktop ) the deinterlacing is working whatever the setting of hardware acceleration, and the #2 option from above is NOT missing, even when hardware-accel is inactivated
Deinterlacing is working on exactly no(!) intel hardware with xbmc mainline code. You need to use fernetmenta's master ppa to get correct deinterlacing, see: http://forum.xbmc.org/showthread.php?tid=165707 or use OpenELEC which includes that work.
(2014-07-08, 16:32)fritsch Wrote: [ -> ]Deinterlacing is working on exactly no(!) intel hardware with xbmc mainline code.
Aha!

If this is the case, why then is deinterlacing clearly working on a Haswell system, but über-obviously not on the Celeron system? (xbmc is same version: xbmc 13.1 Git:f2acae7 Compiled June 6 2014)

And why does it result on the Haswell to show the option for chosing the Deinterlace method, while this option is absent on the Celeron?

And why is xbmc not only allowing to chose this option, but sets it even by default, when it knows it isn't working on its host machine?
https://github.com/xbmc/xbmc/blob/master....cpp#L2712 <- read

xbmc mainline does show two different deinterlacing modes when vaapi is in use: BOB and Inverted.

If your hsw xbmc cannot open the relevant libva-driver-intel it falls back to software and shows the sw decoding options.

So in short: When you see Software Blend, Deinterlace, Weave and so on ... hw acceleration is non working -> your Debug Log will show that.
(2014-07-09, 13:37)fritsch Wrote: [ -> ]https://github.com/xbmc/xbmc/blob/master....cpp#L2712 <- read
You are expecting too much of me Big Grin

I looked at the logs and found various "error" and "not-supported" stuff in regard to vaapi, which I now take as meaning that I'll have to do it in software and wait for future updates. Is good enough, and CPU load is low enough, at least for the time being with SD quality video.

Thanks for enlightening me. At least the software deinterlacing allowed watching the historic German:Brasil 7:1 match seeing real footballs, and not flying hedgehogsCool
How about posting the Debug Log - would save us a lot of time.

Edit: The historical game was transmitted in 720p50, at least on ARD HD / ZDF HD
(2014-07-09, 17:39)fritsch Wrote: [ -> ]How about posting the Debug Log - would save us a lot of time.

Edit: The historical game was transmitted in 720p50, at least on ARD HD / ZDF HD

As you wish: (in both cases VAAPI is set to be allowed)
logs for the Haswell case: http://xbmclogs.com/show.php?id=243332 -- Interlacing is ok, picture is decent
logs for Celeron (MSI dc111) case: http://xbmclogs.com/show.php?id=243334 -- Interlacing is VERY bad, poor picture, though De-interlace was set to "Active"

Couldn't watch the game in HD, only SD was available to me. I need to upgrade and hope for the 8-channel SAT>IP LNB (http://forum.xbmc.org/showthread.php?tid...pid1732750), which is why I am looking harder into tvheadend and xbmc.
Your version of vaapi was released before Haswell.I will never understand why users stick with such old drivers for HTPC usage.
As expected:
HSW System
Quote:17:55:58 T:139634956826368 DEBUG: CDVDPlayerVideo - CDVDMsg::GENERAL_RESYNC(0.000000, 1)
17:55:58 T:139634956826368 DEBUG: VAAPI - attempting to open codec 2 with profile 4 at level 8 with 1 reference frames
17:55:58 T:139634956826368 DEBUG: VAAPI - initialize version 0.32
17:55:58 T:139634956826368 ERROR: VAAPI - unable to initialize display -1 - unknown libva erro

You seem to be missing the relevant driver -> fallback to Software


Celeron:
Quote:OpenMax:no libstagefright:no VDPAU:yes VAAPI:yes
18:05:06 T:140089476769536 DEBUG: FactoryCodec - Video: - Opening
18:05:06 T:140089476769536 NOTICE: CDVDVideoCodecFFmpeg::Open() Using codec: MPEG-2 video
18:05:06 T:140089476769536 DEBUG: FactoryCodec - Video: ff-mpeg2video - Opened
18:05:06 T:140089468376832 DEBUG: CDVDPlayerVideo - CDVDMsg::GENERAL_RESYNC(0.000000, 1)
18:05:06 T:140089468376832 DEBUG: VAAPI - attempting to open codec 2 with profile 4 at level 8 with 1 reference frames
18:05:06 T:140089468376832 DEBUG: VAAPI - initialize version 0.32
18:05:06 T:140089468376832 DEBUG: VAAPI - vendor: Intel i965 driver - 1.0.15
18:05:06 T:140089468376832 DEBUG: VAAPI - deinterlace not support on this intel driver version
18:05:06 T:140089468376832 DEBUG: VAAPI - profile 0
18:05:06 T:140089468376832 DEBUG: VAAPI - profile 1
18:05:06 T:140089468376832 DEBUG: VAAPI - profile 5
18:05:06 T:140089468376832 DEBUG: VAAPI - profile 6
18:05:06 T:140089468376832 DEBUG: VAAPI - profile 7
18:05:06 T:140089468376832 DEBUG: VAAPI - profile 8
18:05:06 T:140089468376832 DEBUG: VAAPI - profile 9
18:05:06 T:140089468376832 DEBUG: VAAPI - profile 10
VAAPI is in use.
HSW needs at least libva-driver-intel >= 1.3.0 -> upgrade to Ubuntu 14.04 LTS or follow the howto I linked with my reply.

12.04.4 provides much too old vaapi drivers, furthermore the kernel it is using is too old, that fucks up Limited / Full Color Range.
I am not emotionally attached to any particular driverSmile, but when your system is fully up to date, how would one know that something is missing?

The kernel and the libva are identical versions in both computers, and that kernel is from trusty 14.04:
uname -a: 3.13.0-30-generic #55~precise1-Ubuntu SMP Fri Jul 4 21:52:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
libva-intel-vaapi-driver: 1.0.15-1ubuntu2

@fritsch: What Howto-Link are you referring to? I only see links to the FAQ and Debug Log; neither has anything on vaapi?
Quote:The kernel and the libva are identical versions in both computers, and that kernel is from trusty 14.04:
uname -a: 3.13.0-30-generic #55~precise1-Ubuntu SMP Fri Jul 4 21:52:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
libva-intel-vaapi-driver: 1.0.15-1ubuntu2

One is IVB the other one is HSW. -> IVB works, HSW does not ....
@FernetMenta: thats why I suggested to check for proper driver versions Wink
Checking the VA version is easy, but checking the driver version needs "parsing of a string" which can change, that was the reason we decided against it.
Pages: 1 2 3 4