First : I still have field parity problems with interlaced material on
interlaced TV.
Always, sometimes, coming and going, or just the odd glitch?
MPEG-2 can represent video with either field parity so you need to make sure you've got the necessary plumbing to set the field parity of the DirectFB layer correctly based on the top_field_first flag from the MPEG video (and made available by latest libcle266mpegdec but not the original).
In DirectFB, you need to enable DLOP_FIELD_PARITY on the video layer and you'll need the DirectFB viafb module (the current field cannot be detected except by the kernel driver).
* applied viafb_flip_ioctl.patch from Mark Adams (transfered by Rolf
Ahrenberg and Laz today)
* this patch is really old, and does not apply totally cleanly on
today's CVS
* attached is un updated patch against current CVS (maybe Mark could
apply it to CVS if he have no better idea now about how to implement that ?)
I can do. However, the other half of it (the patch to the unichome driver) is more tricky because the DirectFB driver needs to be able to work with any of the many variants of viafb. That means doing some more work on the DirectFB side of things so it can either transparently decide whether or not to use the code from the patch, or so that there's an option to specifically enable it.
* maybe Mark could add his patch to DirectFB CVS (if the freeze for 1.0
still allows that)
See above.
Note: that patch isn't essential for to get the field parity correct (but it does make it a little more reliable if your machine is heavily loaded).
Mark
_______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
