tests/fate/filter-video: Use a bitexact/lossless input sample for fate-filter-metadata-silencedetect
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Signed-off-by: NBela Bodecs <bodecsb@vivanet.hu>
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Some ADTS streams can have multiple ID3 tags between frames. This
change parses all of them, rather than just the first one.
Signed-off-by: NMattias Amnefelt <mattiasa@avm.se>
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Also update fate reference. Fixes ticket #6675.

Fate output changes and under close inspection looks more correct.
Fixes #6187.
Signed-off-by: NPaul B Mahol <onemda@gmail.com>

On modern x86 systems its around 2x faster. For systems without
FPUs it'll be slower, but our policy is to prefer floating point
implementations and to let users decide what's best (or just not
compile them on systems without FPUs).
Signed-off-by: NRostislav Pehlivanov <atomnuker@gmail.com>

Set relevant filter parameters such that the result can easily be
checked with a waveform editor.
In particular, it makes it clear the silence_start is not accurate in
the current code.

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

Signed-off-by: NSasi Inguva <isasi@isasi.mtv.corp.google.com>
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

test extract color and alpha
with the three main kind of hap frame :
- no snappy compression
- snappy compression and one chunk
- snappy compression and several chunks (16 here)

like the bsf filter need to be used with vtag and encoder edition
also test the information of the target mov for color and alpha

This adds a way for an API user to transfer QP data and metadata without
having to keep the reference to AVFrame, and without having to
explicitly care about QP APIs. It might also provide a way to finally
remove the deprecated QP related fields. In the end, the QP table should
be handled in a very similar way to e.g. AV_FRAME_DATA_MOTION_VECTORS.

There are two side data types, because I didn't care about having to
repack the QP data so the table and the metadata are in a single
AVBufferRef. Otherwise it would have either required a copy on decoding
(extra slowdown for something as obscure as the QP data), or would have
required making intrusive changes to the codecs which support export of
this data.

The new side data types are added under deprecation guards, because I
don't intend to change the status of the QP export as being deprecated
(as it was before this patch too).

the test in none mode can be let (they don't use libsnappy)

enable dump bit stream filter and update opt fate test ref.
Signed-off-by: NJun Zhao <mypopydev@gmail.com>
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

with and without snappy compression
with chunk 1 or chunk 16
for hap, hapa, and hapq

Any parameter set shall have start code of at least 4 byte size.
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Fixes fate on big-endian.

To make the best use of existing code, I generalised the wrapper
that currently does yuv420p10 to p010 to support any mixture of
input and output sizes between 10 and 16 bits. This had the side
effect of yielding a working code path for all yuv420p1x formats
to p01x.

External headers are no longer welcome in the ffmpeg codebase because they
increase the maintenance burden. However, in the NVidia case the vanilla
headers need some modifications to be usable in ffmpeg therefore we still
provide them, but in a separate repository.

The external headers can be found at
https://git.videolan.org/?p=ffmpeg/nv-codec-headers.git

Fate-source is updated because of the deleted files, and dynlink_loader.h
license headers were updated with the standard FFmpeg headers.
Signed-off-by: NMarton Balint <cus@passwd.hu>
Signed-off-by: NTimo Rothenpieler <timo@rothenpieler.org>

ticket 6994

(e.g. nv12)

Regression since 7b19e76a

This is needed by later hwaccel code to tell which encoding process was
used for a particular frame, because hardware decoders may only support a
subset of possible methods.

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

Signed-off-by: NTobias Rapp <t.rapp@noa-archive.com>

These tests cover specific rounding behaviour, to ensure that I don't
introduce any regressions with the rewritten "activate" callback based
fps filter.
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

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

Broken by d23fff0d.

A basic test for demuxing raw AAC (ADTS) with ID3v2 tags.

In 16x8 motion compensation, for lower 16x8 region, the input to mpeg_motion() for motion_y was "motion_y + 16", which causes wrong rounding. For 4:2:0, chroma scaling for y is dividing by two and rounding toward zero. When motion_y < 0 and motion_y + 16 > 0, the rounding direction of "motion_y" and "motion_y + 16" is different and rounding "motion_y + 16" would be incorrect.

We should input "motion_y" as is to round correctly. I add "is_16x8" flag to do that.
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

For B field pictures, the spec says,

> The prediction shall be made from the field of the same parity as the field being predicted.

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

Adds basic unit test for parsing ID3v2 tags.
Signed-off-by: NJames Almer <jamrial@gmail.com>

This is done mainly in preparation for the SIMD patches.

- for the 8-bit input, decrease the blend factor precision to 7-bit.
- for the 16-bit input, increase the blend factor precision to 15-bit.
- make sure the blend functions are not called with 0 or maximum blending
  factors, because we don't want the signed factor integers to overflow.

Fate test changes are due to different rounding.
Signed-off-by: NMarton Balint <cus@passwd.hu>

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

Signed-off-by: NMarton Balint <cus@passwd.hu>

<jamrial> durandal_1707: 8088b5d6 broke the acrossfade test
<@durandal_1707> jamrial: there was test?
<jamrial> durandal_1707: fate-filter-acrossfade
<@durandal_1707> what broke?
<jamrial> what used to be one frame is now two
<@durandal_1707> ahh, just update test
Signed-off-by: NJames Almer <jamrial@gmail.com>

The framerate filter was quite convoluted with some filter_frame /
request_frame logic bugs. It seemed easier to rewrite the whole filter_frame /
request_frame part and also the frame interpolation ratio calculation part in
one step.

Notable changes:
- The filter now only stores 2 frames instead of 3
- filter_frame outputs all the frames it can to be able to handle consecutive
  filter_frame calls which previously caused early drops of buffered frames.
- because of this, request_frame is largely simplified and it only outputs
  frames on flush. Previously consecuitve request_frame calls could cause the
  filter to think it is in flush mode filling its buffer with the same frames
  causing a "ghost" effect on the output.
- PTS discontinuities are handled better
- frames with unknown PTS values are now dropped

Fixes ticket #4870.
Probably fixes ticket #5493.
Signed-off-by: NMarton Balint <cus@passwd.hu>

The PERSIST_RPARAM_A_RExt_Sony_1 bitstream has an out-of-range value
and has therefore been superseded.
It is otherwise identical, and decodes the same.
Signed-off-by: NJames Almer <jamrial@gmail.com>

It was truncated to int later on anyway. Fate test changes are due to rounding
instead of truncation.

Fixes fate test failures on x86-32 (gcc 4.8 (Ubuntu 4.8.5-2ubuntu1~14.04.1))
after 090b7406.
Signed-off-by: NMarton Balint <cus@passwd.hu>