On Mon, Feb 16, 2009 at 01:29:22PM +0000, Tony Houghton wrote:
On Mon, 16 Feb 2009 13:26:18 +1000 Torgeir Veimo torgeir@pobox.com wrote:
Andy Ritger (nvidia) said in a mail to the xorg mailing list some time ago;
"If the application doesn't enable de-interlacing, NVIDIA's VDPAU implementation will currently copy the weaved frame to the "progressive" surface, and whether it will come out correctly will depend whether the window's offset from the start of the screen is odd or even."
I take this to imply that field parity should be possible, but the application in use have to detect the field flag from the source material and set the Y offset appropriately to be 0 or 1 accordingly.
It also relies on vsyncing correctly. If it syncs to the wrong field you'll get the backward juddering. I don't think VDPAU provides a way for applications to distinguish between odd and even vsyncs, but perhaps it does its own internal syncing.
Might be a good idea to ask Andy Ritger about that vsync to correct fields..
Hopefully Nvidia is able to fix/provide that.. VPDAU seems good otherwise..
-- Pasi