[FFmpeg-devel] [RFC] H.264 decoding error spam with max_num_ref_frames = 0

Jason Garrett-Glaser darkshikari
Mon Sep 27 06:49:02 CEST 2010

I wrote a patch today to add AVC-Intra support to x264.  This requires
that max_num_ref_frames be set to 0, which is fitting, given that the
stream is all intra.  Apparently nobody ever tested ffmpeg with this
-- when decoding such a stream, a massive flood of "number of
reference frames exceeds max (probably corrupt input), discarding one"
messages ensues.

This is likely because ffmpeg attempts to store the frames in the DPB
anyways, even though, technically there isn't a DPB at all.

Ideas for a fix, besides just hacking ffmpeg to not print that message
in this specific case?  Attached is a very short file that causes

Dark Shikari
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.h264
Type: video/h264
Size: 16033 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20100926/ec2ad282/attachment.bin>

More information about the ffmpeg-devel mailing list