Signed-off-by: NGyan Doshi <ffmpeg@gyani.pro>

Optimize theora decoding with mmi in functions:
1. ff_vp3_idct_add_mmi
2. ff_vp3_idct_put_mmi
3. ff_vp3_idct_dc_add_mmi
4. ff_put_no_rnd_pixels_l2_mmi

Theora decoding speed improved about 32%(from 88fps to 116fps, Tested on loongson 3A3000).
Reviewed-by: NShiyou Yin <yinshiyou-hf@loongson.cn>
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Fixes: Out of array access
Fixes: 13090/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_MPEG4_fuzzer-5408668986638336

Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpegReviewed-by: NKieran Kunhya <kierank@obe.tv>
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

I forgot to add the version bump and changelog within the changes.

This is the equivalent change for cuviddec after the previous change
for nvdec. I made similar changes to the copying routines to handle
pixel formats in a more generic way.

Note that unlike with nvdec, there is no confusion about the ability
of a codec to output 444 formats. This is because the cuvid parser is
used, meaning that 444 JPEG content is still indicated as using a 420
output format.

With the introduction of HEVC 444 support, we technically have two
codecs that can handle 444 - HEVC and MJPEG. In the case of MJPEG,
it can decode, but can only output one of the semi-planar formats.

That means we need additional logic to decide whether to use a
444 output format or not.

The latest generation video decoder on the Turing chips supports
decoding HEVC 4:4:4. Supporting this is relatively straight-forward;
we need to account for the different chroma format and pick the
right output and sw formats at the right times.

There was one bug which was the hard-coded assumption that the
first chroma plane would be half-height; I fixed this to use the
actual shift value on the plane.

We also need to pass the SPS and PPS range extension flags.

We need all the flags to be exposed to be able to pass them on to
HW decoders. I did not attempt to nuance any of the warnings about
flags being unsupported as there's no way, at the point we extract
flags, to say whether an HW decoder is being used.

Why did this not break compilation?

Fixes: NULL pointer dereference
Fixes: clusterfuzz-testcase-minimized-audio_decoder_fuzzer-5634316373721088
Reported-by: NChris Cunningham <chcunningham@google.com>
Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>

Signed-off-by: NTimo Rothenpieler <timo@rothenpieler.org>

This removes lots of code duplication and also allows more complex specifiers,
for example you can use p:204:a:m:language:eng to select the English language
audio stream from program 204.
Signed-off-by: NMarton Balint <cus@passwd.hu>

The default codepage (ISO6937) should be used in this case.
Signed-off-by: NMarton Balint <cus@passwd.hu>

ISO-10646 alone means UCS-4 for iconv, the specs refers to the Basic
Multilingual Plane (BMP), therefore we need UCS-2. VLC also using that.
Signed-off-by: NMarton Balint <cus@passwd.hu>

Signed-off-by: NGyan Doshi <ffmpeg@gyani.pro>

Correct the comment
Signed-off-by: NJun Zhao <mypopydev@gmail.com>

Signed-off-by: NMoritz Barsnick <barsnick@gmx.net>

Fixes some rather embarrassing mistakes that somehow passed my
eyes.

* Now catches if memory allocation has failed during bprint usage
  by checking av_bprint_is_complete().
* Now catches if adding an ASS rectangle into an AVSubtitle failed.
* Returns AVERROR_INVALIDDATA if we get an invalid region buffer
  length.

Use av_ts2str() for AVFrame.pkt_dts/pts to avoid print the
pkt_dts/pts as negative number like:
"0,    3616613, -9223372036854775808,     1001,  3110400, 0x75e37a65"
Reviewed-by: NMichael Niedermayer <michael@niedermayer.cc>
Signed-off-by: NJun Zhao <mypopydev@gmail.com>

Fix build warning like "warning: ISO C90 forbids mixed declarations
and code" after adjust the location for malloc fail check.
Reviewed-by: NMichael Niedermayer <michaelni@gmx.at>
Signed-off-by: NJun Zhao <mypopydev@gmail.com>

Need to check malloc fail before using it, so adjust the location
in the code.
Reviewed-by: NMichael Niedermayer <michaelni@gmx.at>
Signed-off-by: NJun Zhao <mypopydev@gmail.com>

If we enable a component but a dependant library is disabled, then the enabled
component gets silently disabled. Warning about disabled explicitly enabled components
allows configure to show the missing dependencies and if --fatal-warnings is
used it can also fail if the user wants it so.

For example if libdav1d is not availble ./configure --enable-decoder=libdav1d
succeeds but the libdav1d decoder is not be enabled. After the patch configure
will warn about this:

WARNING: Disabled libdav1d_decoder because not all dependencies are satisfied: libdav1d
Signed-off-by: NMarton Balint <cus@passwd.hu>

Binary searching would hang if the fragment items do NOT have timestamp for the
specified stream.

For example, a fmp4 consists of separated 'moof' boxes for each track, and
separated 'sidx' for each segment, but no 'mfra' box.  Then every fragment item
only have the timestamp for one of its tracks.

Example:
ffmpeg -f lavfi -i testsrc -f lavfi -i sine -movflags dash+frag_keyframe+skip_trailer+separate_moof -t 1 out.mp4
ffmpeg -ss 0.5 -i out.mp4 -f null none

Also fixes the hang in ticket #7572, but not the reason for having
AV_NOPTS_VALUE timestamps there.
Signed-off-by: NCharles Liu <liuchh83@gmail.com>
Signed-off-by: NMarton Balint <cus@passwd.hu>

Simplifies code.
Reviewed-by: NMichael Niedermayer <michaelni@gmx.at>
Signed-off-by: NJames Almer <jamrial@gmail.com>

Signed-off-by: NGyan Doshi <ffmpeg@gyani.pro>

Reviewed-by: jkqxz
Signed-off-by: NJames Almer <jamrial@gmail.com>

While the image2pipe demuxer ignores the option - confusing users -
the autodetecting demuxers that are favoured over image2 act on it.

Found with the help of codespell-1.14.0.
Signed-off-by: NMoritz Barsnick <barsnick@gmx.net>
Signed-off-by: NGyan Doshi <ffmpeg@gyani.pro>

Signed-off-by: NGyan Doshi <ffmpeg@gyani.pro>

when set option fmp4_init_filename to init_%v.mp4
before patch:
the init file will be init_%v_0.mp4, init_%v_1.mp4
after patch:
the init file will be init_0.mp4, init_1.mp4
Reported-By: NGyan Doshi <ffmpeg@gyani.pro>
Signed-off-by: NSteven Liu <lq@chinaffmpeg.org>