Note that convergence_duration had another meaning, one which was in
practice never used. The only real use for it was a 64 bit replacement
for the duration field. It's better just to make duration 64 bits, and
to get rid of it.

Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>

Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>

Convert doxygen to multiline and express bitfields more simply.

Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>

Signed-off-by: Diego Biurrun <diego@biurrun.de>

Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
Signed-off-by: Justin Ruggles <justin.ruggles@gmail.com>

The ParserContext class doesn't have an AVClass, required for
using it as a logging class.

Signed-off-by: Martin Storsjö <martin@martin.st>

Signed-off-by: Martin Storsjö <martin@martin.st>

Signed-off-by: Diego Biurrun <diego@biurrun.de>

Signed-off-by: Diego Biurrun <diego@biurrun.de>

Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>

Fix the breakage introduced with 9073ca6c6e

Fixes build with the bump, since the prototype is already marked for
removal.

Signed-off-by: Mans Rullgard <mans@mansr.com>

It was being set wrong for files with data_offset > 0

Patch by Michael Chinen, mchinen gmail

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

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

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

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

next_frame_offset are not set, because second field has next frame offset set
but not frame_offset, otherwise this wrongly fetch timestamp for the
second field.

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

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

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

this should greatly simplify handling of packet pos.

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

unit in fetch_timestamp(). This should make no difference for valid
streams but may help invalid ones, also its needed for future changes.

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

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 17574 to svn://svn.ffmpeg.org/ffmpeg/trunk

Patch by Ivan Schreter, schreter gmx net

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

Initialized to -1 in parser.c for backward compatibility.

Patch by Ivan Schreter, schreter gmx net

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

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

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

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

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

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

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

piecewise, thus the end values cannot be used for associating timestamps.

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