[FFmpeg-devel] [PATCH]Assume STRICT for h264.c

Michael Niedermayer michaelni
Thu Nov 12 04:34:16 CET 2009

On Wed, Nov 11, 2009 at 11:11:14PM +0000, Carl Eugen Hoyos wrote:
> Michael Niedermayer <michaelni <at> gmx.at> writes:
> > ref_frame_count is as the name indicates something about reference frames
> > has_b_frames represents the size of the reordering buffer and thus is a
> > very poor name (historic reasons why its as it is, if it wherent public API
> > we could fix it ...)
> Thank you for the useful explanation (and the fix)!
> Could you also explain why h->delayed_pic[0]->key_frame is constantly 1 for this
> stream?

Because its constantly the same keyframe until the next keyframe.
This stream just contains B and I frames, all the B frames are reordered
to prior the previous I frame. (that is the I frame is delayed and output


Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Many that live deserve death. And some that die deserve life. Can you give
it to them? Then do not be too eager to deal out death in judgement. For
even the very wise cannot see all ends. -- Gandalf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20091112/f3249625/attachment.pgp>

More information about the ffmpeg-devel mailing list