[mythtv-users] Playback On Intel

[Cédric Schieli]

2014-05-12 14:50 GMT+02:00 David Edwards <david at more.fool.me.uk>:

> I can't remember having had any segfaults yet, but it's great to hear
> VAAPI is getting some love.
>

The bug was only triggered if the decoded frame height was not exactly the
same as the display height (eg. 1088 instead of 1080), so if you only used
true HD material (exact 1080p or 1080i) in your tests you couldn't be hit.


> It sounds like they're working on supporting software deinterlacing so
> as not to be constrained by the VAAPI library. I would still be
> interested to know why the Motion Adaptive deinterlacer is not
> available in Mythfrontend even though the Intel release notes claim it
> is now supported on Haswell.
>

In order to benefit from the hw deinterlacers available on the different
Intel platforms it is necessary to use an extension of the VAAPI (the video
processing interface, aka VPP, which was added in libva-1.2.0 in June 2013)
to setup a postprocessing pipeline. It is also necessay that the
libva-intel-driver implements the corresponding deinterlacer for your
device. As of libva-intel-driver-1.3.0 you'll get :

- Broadwell: Bob, MotionAdaptive, MotionCompensated
- Haswell: Bob, MotionAdaptive, MotionCompensated
- Ivy Bridge: Bob, MotionAdaptive
- Sandy Bridge: Bob

For now, the pipeline setup has not been implemented in MythTV, that's why
it's not available in the profiles. I may look at this in a not so distant
future, but don't hold your breath...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140512/1296864e/attachment.html>