Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

treat this the same as an over-sized superframe packet to break out of
the parser loop and allow the decoder to fail.
Reviewed-by: NRonald S. Bultje <rsbultje@gmail.com>
Signed-off-by: NJames Zern <jzern@google.com>

Signed-off-by: NMatt Oliver <protogonoi@gmail.com>

Signed-off-by: NMatt Oliver <protogonoi@gmail.com>

Example:

% ./ffmpeg -h encoder=aac
  -aac_coder         <int>        E...A... Coding algorithm (from -1 to 3) (default twoloop)
     faac                         E...A... FAAC-inspired method
     anmr                         E...A... ANMR method
     twoloop                      E...A... Two loop searching method
     fast                         E...A... Constant quantizer
[...]

Signed-off-by: NKyle Swanson <k@ylo.ph>
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

These functions return an error typically when the key size is an
incorrect number. AVERROR(EINVAL) is more specific than -1.
Reviewed-by: NRonald S. Bultje <rsbultje@gmail.com>
Reviewed-by: NMichael Niedermayer <michael@niedermayer.cc>
Signed-off-by: NGanesh Ajjanagadde <gajjanagadde@gmail.com>

Reviewed-by: NPaul B Mahol <onemda@gmail.com>
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Signed-off-by: NPaul B Mahol <onemda@gmail.com>

Commit 3a0a2f33 claims large performance
advantages for AV_QSORT over libc's qsort. The reason is that I suspect
that libc's qsort (at least on non LTO builds, like the typical FFmpeg config)
can't inline the comparison callback:
https://stackoverflow.com/questions/5290695/is-there-any-way-a-c-c-compiler-can-inline-a-c-callback-function.
AV_QSORT has two things going for it:
1. The guaranteed inlining of qsort itself. This yields a negligible
boost that may be ignored.
2. The more serious possibility of potentially allowing the comparison
function to be inlined - this is likely responsible for the large boosts
reported.

There is a comment explaining that this is a place that could use some
performance improvement. Thus AV_QSORT is used to achieve that.

Benchmarks deemed unnecessary due to existing claims about AV_QSORT.
Tested with FATE.
Reviewed-by: NMichael Niedermayer <michael@niedermayer.cc>
Signed-off-by: NGanesh Ajjanagadde <gajjanagadde@gmail.com>

libavutil was always built, allow its dependencies to be enabled.

Signed-off-by: NPaul B Mahol <onemda@gmail.com>

Signed-off-by: NPaul B Mahol <onemda@gmail.com>

When the encoder is fed with less frames than its delay, the picture list looks like { NULL, NULL, ..., frame, frame, frame }. When flushing the encoder (input frame == NULL), we need to ensure the picture list is shifted enough so that we do not return an empty packet, which would mean the encoder has finished, while it has not encoded any frame.

Before the patch, the command:
'./ffmpeg_g -loglevel debug -f lavfi -i "testsrc=d=0.01" -bf 2 -vcodec mpeg2video out.mxf' prints:

Output stream #0:0 (video): 1 frames encoded; 0 packets muxed (0 bytes);

After:

Output stream #0:0 (video): 1 frames encoded; 1 packets muxed (8058 bytes);

Relates to ticket #4817.
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Signed-off-by: NPaul B Mahol <onemda@gmail.com>

This clarifies and adds Doxygen for ff_fmt_is_in.
Reviewed-by: NTimothy Gu <timothygu99@gmail.com>
Signed-off-by: NGanesh Ajjanagadde <gajjanagadde@gmail.com>

There were some errors in the calculation as well as an entire
unnecessary loop to find the gain coefficient. Merge the
two loops.
Thanks to @ubitux for the suggestions and testing.

Having it as a float didn't even allow enough precision to check
for INT_MAX/2.
Signed-off-by: NDerek Buitenhuis <derek.buitenhuis@gmail.com>

Having it as a float didn't even allow enough precision to check
for INT_MAX/2.
Signed-off-by: NDerek Buitenhuis <derek.buitenhuis@gmail.com>

Signed-off-by: NPaul B Mahol <onemda@gmail.com>

avcodec/aacenc: Fix "libavcodec/aacenc.c:540:13: warning: ISO C90 forbids mixed declarations and code"
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

This makes it consistent with ffprobe
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Fixes ticket #4924.
Found-by: NJaroslav Šnajdr <jsnajdr@gmail.com>
Reviewed-by: NNicolas George <george@nsup.org>
Signed-off-by: NMarton Balint <cus@passwd.hu>

av_warn_unused_result is added to functions whose return status should
be checked. Currently does not trigger any warnings, but should be
useful for future robustness.
Reviewed-by: NMichael Niedermayer <michael@niedermayer.cc>
Signed-off-by: NGanesh Ajjanagadde <gajjanagadde@gmail.com>

The wtv demuxer doesn't reference any functionality from asfdec or asfcrypt

The fate test command line is supposed to serve as an example. It's
nicer to explicitly state the profile rather than setting options
to force it for you.

Suggested by ubitux.
Convenient.

A value of 2048 will overflow 11 bits.

Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Fixes make fate V=2
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Fails on some newer systems (archlinux with a modern GCC version).

Since it became the default option, in order to prevent interference
with the other tests, disable it.

In light of the recent changes to the TNS system, it has been
deemed worthy and robust enough to be turned on by default.