[FFmpeg-devel] [RFC] h264 avoid starting decode on a non top field

Michael Niedermayer michaelni at gmx.at
Fri Nov 11 23:11:35 CET 2011


On Fri, Nov 11, 2011 at 09:03:04PM +0100, Joakim Plate wrote:
> Hi, 
> 
> This is hack/fix for a mpegts live stream sample we've encountered. I may
> be able to provide it, but i'll have to check with source.
> 
> After some seeks (ie not always), we'd get a continous errors like:
> 
> [h264 @ 0xa87a1e0] illegal short term buffer state detected
> [h264 @ 0xa87a1e0] Missing reference picture
>     Last message repeated 53 times274KB vq=15107KB sq=    0B f=1/82
> [h264 @ 0xa87a1e0] mmco: unref short failure
>     Last message repeated 1 times
> [h264 @ 0xa87a1e0] illegal short term buffer state detected
> [h264 @ 0xa87a1e0] Missing reference picture5084KB sq=    0B f=1/83
>     Last message repeated 11 times
> [h264 @ 0xa87a1e0] illegal short term buffer state detected
> 
> It seems it starts decode on wrong field and then doesn't recovers. I'm not
> sure if h264 mandates top field first in bitstream, if not there is
> probably something better to check. But this seems logical.

i dont think theres any gurantee that the top field will be first

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Old school: Use the lowest level language in which you can solve the problem
            conveniently.
New school: Use the highest level language in which the latest supercomputer
            can solve the problem without the user falling asleep waiting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20111111/55660689/attachment.asc>


More information about the ffmpeg-devel mailing list