of calling it at the end of a frame with a large negative offset.
This significantly reduces the maximal distance in container packets between
the point where the first byte of the "access unit" was stored and where
we call ff_fetch_timestamp() thus reducing the constraints on our parser.
Also change the parser from next_frame_offset to cur, this is needed
because now the reference is from container packet start instead of
frame start. (i previously misinterpreted this as bug)

Originally committed as revision 17731 to svn://svn.ffmpeg.org/ffmpeg/trunk

Patch by Ivan Schreter, schreter gmx net

Originally committed as revision 17572 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 16684 to svn://svn.ffmpeg.org/ffmpeg/trunk

contains the first picture startcode that commences in the PES
packet, instead of the first access unit that commences in the
PES packet. Fix the parser to
handle that properly. This was a very long standing bug ...
The change to the seek regressions is because the mpeg ts muxer
stores too many invalid and randomized timestamps which overflow
the 4 entry buffer we use in the parser.

Originally committed as revision 13643 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 12684 to svn://svn.ffmpeg.org/ffmpeg/trunk

Log:
Make timestamp interpolation work with mpeg2 field pictures.
Cleaner/simpler solutions are welcome.
----
A IMHO cleaner solution has been implemented.

Originally committed as revision 12162 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 12161 to svn://svn.ffmpeg.org/ffmpeg/trunk

Cleaner/simpler solutions are welcome.

Originally committed as revision 12156 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 8921 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 8902 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 8901 to svn://svn.ffmpeg.org/ffmpeg/trunk