avcodec_set_dimensions() is supposed to be an internal utility function,
there is no reason whatsoever for it to be public. Therefore deprecate
it.

This can be optionally disabled whith the "output_corrupt" flags
option.  When in "output_corrupt" mode, incomplete frames are
signalled through AVFrame.flags FRAME_FLAG_INCOMPLETE_FRAME.
Signed-off-by: NAnton Khirnov <anton@khirnov.net>

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

This was added in 9b07a2dc as an ABI hack to allow older
code built with lavf 52 to register protocols even if the size
of the URLProtocol struct was increased. Later, registering
protocols from outside of lavf was removed and this workaround
isn't needed any longer since lavf 53.

This removes an unchecked malloc and a memory leak for the cases
when this workaround actually was used - which it hasn't since
lavf 53.
Signed-off-by: NMartin Storsjö <martin@martin.st>

Also typedef the private data struct and make its name consistent with
the rest of Libav.
Signed-off-by: NVittorio Giovara <vittorio.giovara@gmail.com>
Signed-off-by: NAnton Khirnov <anton@khirnov.net>

$(STRIP) always expands to something, because it is one of the commands
in the BRIEF list. This renders the condition pointless.
Signed-off-by: NIngo Brückl <ib@wupperonline.de>
Signed-off-by: NDerek Buitenhuis <derek.buitenhuis@gmail.com>

Signed-off-by: NDerek Buitenhuis <derek.buitenhuis@gmail.com>

It is private and must not be touched from outside of lavf.

avconv abuses the API by accessing AVStream.parser (which is private).
Removing AVStream.reference_dts in
2ba68dd0 breaks ABI compatibility for an
old avconv using a newer lavf. Fix this by adding a dummy field until
the next bump.

Signed-off-by: NDerek Buitenhuis <derek.buitenhuis@gmail.com>

Signed-off-by: NDerek Buitenhuis <derek.buitenhuis@gmail.com>

Fixes corrupt data errors when downmixing in the AC-3 decoder.
Signed-off-by: NMichael Niedermayer <michaelni@gmx.at>
Signed-off-by: NJustin Ruggles <justin.ruggles@gmail.com>

CC:libav-stable@libav.org

This isn't a set of flags but just a plain integer in the range
6-8.
Signed-off-by: NMartin Storsjö <martin@martin.st>

Signed-off-by: NAnton Khirnov <anton@khirnov.net>

Signed-off-by: NAnton Khirnov <anton@khirnov.net>

Just crccheck prints a warning, crccheck+explode returns an error.

Also document this behavior.

err_recognition is supposed to trigger detecting and reporting errors,
not trying to fix them.

And use init_get_bits8 to check for integer overflows while at it.

CC: libav-stable@libav.org
Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>

It is by definition unreliable and causes pointless noise on valid
code.

It does not make sense in the vast majority of use cases, no currently
defined AV_OPT_TYPE_FLAGS options in Libav set the range to anything
nontrivial, and many of those get it wrong (the "correct" range is
INT_MIN to INT_MAX so that the builtin constant "all" works).

A VUI doesn't contain anything strictly necessary for decoding.
Apparently there are many samples with truncated VUIs in the wild, this
commit should allow decoding them.