On Fri, 2014-03-28 at 17:40 +0000, Simon Farnsworth wrote: > Hello, > > We're currently porting over to use VA-API for all our video display needs, > and we've hit a showstopper. > > Deinterlace on Sandy Bridge hardware (deployed in the field) is awful - it > appears to be bob only. On newer units (Bay Trail, Ivy Bridge), it's able to > use motion adaptive, which looks great. > > The open PRMs for Sandy Bridge suggest that it has a very similar motion > adaptive deinterlacer to Ivy Bridge; is there any reason why it's not enabled > in libva 1.3.0?
Yes, only BobDI is supported on SNB, and it isn't optimized in the driver. We might support the optimized BobDI and motion adaptive DI once we get a chance to spend some time on the legacy platform. > > I need motion adaptive for Sandy Bridge to make it possible for me to replace > software decode with libva; this, in turn, is a gating factor for introducing > Haswell and Bay Trail silicon to our market. _______________________________________________ Libva mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libva
