On Mon, Nov 28, 2011 at 06:51:05PM +0100, Luca Barbato wrote:
> On 11/28/11 12:28 PM, Janne Grunau wrote:
> >I have no idea what v4l2 drivers typically return for V4L2_FIELD_ANY
> >but there are more interlaced formats than V4L2_FIELD_INTERLACED.
>
> I can try to map/support all of them. But I just have progressive
> usb cameras handy...
I was more thinking about erroring out on anything other than
_INTERLACED or _PROGRESSIVE. Handling V4L2_FIELD_INTERLACED_{TB,BT} and
setting the field order accordingly.
After looking at v4l2 driver source V4L2_FIELD_{TOP,BOTTOM} has to be
supported too. If the capture height is smaller than fullheight/2 just
one field is returned.
insert $curse about inconsistencies in V4L2 drivers
> I'd like to refresh this codebase soon anyway.
Go ahead, the function to determine the field order is dubious at best.
Janne
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
