[mythtv] deinterlacers on AMD/ATI VDPAU

Warpme warpme at o2.pl
Sat Nov 30 19:15:40 UTC 2013


On 30/11/13 13:00, Jean-Yves Avenard wrote:
> Hi
>
> On Saturday, November 30, 2013, Warpme wrote:
>
>     Hi all.
>
>     I'm working on adding AMD/ATI HW accell to my project.
>     Hw accel. works OK - but I have q about deinterlacers and VDPAU.
>     Currently MythTV for VDPAU allows to choose deinterlacers mainly
>     from Nvidia hardware based set.
>     When user has AMD/ATI gfx and uses HW accell based on Mesa/UVD -
>     Nvidia deinterlacers doesn't make sense.
>
>     My Q is: is limitation of aval. deint. in VDPAU (Nv subset)
>     because of arbitrary choice or rather it is because supported data
>     flow (in Nv decoder out is fed to deint. in Nv hw. For other
>     setups it will need copy video frame to memory back and forth)?
>
>     br
>     __________________________
>
>
> My understanding is that AMD vdpau driver supports bob and bob 2x.
>
> The deinterlacers available aren't Nvidia only; other chip maker could 
> perfectly supports them should they wanted to.
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-dev
Jean-Yves,

My issue is that under MythTV for VDPAU decoder I can choose only with:

Bob (2x HW)
One Field (1x, HW)
Temporal (1x ,HW)
Advanced (1x ,HW)
Temporal (2x ,HW)
Advanced (2x ,HW)

I not looked into sources, but "HW" suggest me that all those 
deinterlcers are realized in Nv gfx driver/hw - not in MythTV. So for 
non-nv hw/blob they are not working.
On-screen result on AMD/ATI are conforming this: no mater what I select, 
AMD/ATI gives me no-deinterlaced picture.
Maybe I miss something?

br





More information about the mythtv-dev mailing list