Le mercredi 01 mars 2017 à 14:12 +0100, Andrzej Hajda a écrit : > - on output side you have encoded bytestream - you cannot say about > interlacing in such case, so the only valid value is NONE, > - on capture side you have decoded frames, and in this case it > depends > on the device and driver capabilities, if the driver/device does not > support (de-)interlacing (I suppose this is MFC case), interlace type > field should be filled according to decoded bytestream header (on > output > side), but no direct copying from output side!!! I think we need some nuance here for this to actually be usable. If the information is not provided by the driver (yes, hardware is limiting sometimes), it would make sense to copy over the information that userspace provided. Setting NONE is just the worst approximation in my opinion. About MFC, it will be worth trying to read the DISPLAY_STATUS after the headers has been processed. It's not clearly stated in the spec if this will be set or not. Nicolas
Attachment:
signature.asc
Description: This is a digitally signed message part
