2013/4/9 Hendrik Leppkes <h.lepp...@gmail.com> > On Tue, Apr 9, 2013 at 10:16 AM, Yusuke Nakamura < > muken.the.vfrman...@gmail.com> wrote: > > > Attached patches support setting field order information for H.264, VC-1 > > and MPEG-2 video stream by parsing. > > > > > AVCodecContext already has a field order flag, and the parser always gets a > AVCodecContext, duplicating the flag into another struct seems pointless. > > Note that this is also per-frame metadata, and as such a field in a global > struct may not be the best choice, as it can change from frame to frame > (and in properly flagged soft-telecined material, it also does that) > > AVCodecContext.field_order is used only in mov (de)muxer currently. It is used as container level against its documentation: set by libavcodec. When mov container has fiel atom, there may be conflict of field order between CODEC and container. So, at present, this is not duplicated usage. And the current mov (de)muxer doesn't support multiple sample descriptions, so obviously not used per frame/picture.
Yes, field order is per-picture metadata. But where should I place it? I want to get field order without decoding, so AVFrame doesn't help my demand. AVPacket requires parsing frame, so the parser needs field_order after all, I think. _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
