Am 14.07.2014 19:30 schrieb "Vittorio Giovara" <[email protected]>: > > On Fri, Jul 4, 2014 at 11:21 AM, Vittorio Giovara > <[email protected]> wrote: > > --- > > libavutil/frame.h | 4 +++- > > 1 file changed, 3 insertions(+), 1 deletion(-) > > > > diff --git a/libavutil/frame.h b/libavutil/frame.h > > index b2159d3..8685fbb 100644 > > --- a/libavutil/frame.h > > +++ b/libavutil/frame.h > > @@ -171,7 +171,9 @@ typedef struct AVFrame { > > int format; > > > > /** > > - * 1 -> keyframe, 0-> not > > + * frame has no reference to other frames other than itself, so it > > + * may be used as a hint for correct input or output. > > + * This corresponds to H264 IDR frames or HEVC IRAP frames. > > */ > > int key_frame; > > On second thought this piece of documentation does not help much and > this field describes something related to coded frames rather than a > decoded ones (which is what avframe represents). > > So there has been some ideas floating around that it might make sense > to deprecate this field, along a few coded-frame-only others, like > quantizer and psnr. > > Is there any API-user that would be against this proposal? If so, > would a side data for all coded-frame properties be enough for your > needs?
I use keyframe at least to determine if decoding is artifact free after a seek on a bunch of formats, and I'm against changes for the sake of changing it. So IMHO leave it. Note that its also used for encoding to request a keyframe being coded for this frame. - Hendrik _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
