alanwww1 Wrote:Hi !
On Intel side it is also getting better and better. The only thing we miss is VAAPI deinterlacing. Work is already begun, but I am afraid that it will be a long time till we can get that work.
Until that I was thinking to do a software or OpenGL based deinterlacing.
the problem is that i am not so experienced in this area of programming, but I am learning.
Do you think that the way you do it with XVBA, so that deinterlacing is done with OpenGL, can be possible also with VAAPI ?
Thx, Cheers, Alan
As long as there is no advanced de-initerlacing like vdpau temporal or temporal/spatial provided by the hw decoder I would prefer the OpenGL de-interlacing.
Unfortunately XvBA does currently not allow to bypass the deinterlacer when transfering a field from a video surface to a texture. It gives you a de-interlaced frame. Furthermore the API does not provide any settings to influence yuv/rgb conversion which is a negative too.
I have implemented an additional method which reads a video surface back into system memory (pbo) and make use XBMC's NV12 rendering. This method puts more load on the CPU but has better capabilities in terms of deinterlacing.
VAAPI has a function to transfer fields separately. If it's possible to get non deinteralced fields, I would go for this method.