- 30 Nov, 2017 14 commits
-
-
John Stebbins authored
An invalid file may cause huge alloc. Delay expansion of ctts entries until the number of samples is known in mov_build_index. Fixes: 23 Found-by: zhao dongzhuo, AD-lab of Venustech Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
Carl Eugen Hoyos authored
Fixes the following warning: libavfilter/vf_libvmaf.c:179:14: warning: 'main' is usually a function Missed in 5d3e9357
-
James Almer authored
This is required since a5679933Signed-off-by: James Almer <jamrial@gmail.com>
-
James Almer authored
Addresses ticket #6864 Reviewed-by: Michael Niedermayer <michael@niedermayer.cc> Signed-off-by: James Almer <jamrial@gmail.com>
-
James Almer authored
Reviewed-by: Michael Niedermayer <michael@niedermayer.cc> Signed-off-by: James Almer <jamrial@gmail.com>
-
James Almer authored
Signed-off-by: James Almer <jamrial@gmail.com>
-
James Almer authored
This lets us remove one indentation level. Signed-off-by: James Almer <jamrial@gmail.com>
-
James Almer authored
Signed-off-by: James Almer <jamrial@gmail.com>
-
Karthick J authored
This is to take full advantage of Common Media Application Format(CMAF). Now server can generate one content and serve both HLS and DASH players. Reviewed-by: Steven Liu <lq@onvideo.cn>
-
Karthick J authored
-
Steven Robertson authored
The existing logic overrides container metadata even in cases where the container metadata must be trusted (e.g. HDR). The original spec had no provision for specifying color volume, so many files rely on the assumption of Rec. 709. An update to the spec included a 'clv' field for explicitly signaling that the container should be trusted in an existing bitfield in the frame header, but the default of 0 from old encoders forces Rec. 709, which would break any HDR stream. Because there is no place in DNxHR for specifying a transfer function, DNxHR HDR files must include container-level color information. This patch maintains the existing behavior of choosing the 709 over the 601 matrix when container-level information is missing, and allows container-level information to win if present. Signed-off-by: Steven Robertson <steven@strobe.cc> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
James Almer authored
* commit '99e9697e': stereo3d: Support view type for frame sequence type Merged-by: James Almer <jamrial@gmail.com>
-
James Almer authored
* commit '45d7be7f': prores: Always assume limited range This commit is a noop, see 755207dcMerged-by: James Almer <jamrial@gmail.com>
-
James Almer authored
* commit 'b843b343': qsvenc: cavlc option is only available for h264 Merged-by: James Almer <jamrial@gmail.com>
-
- 29 Nov, 2017 15 commits
-
-
Mark Thompson authored
This removes all remaining device-type specificity.
-
Clément Bœsch authored
-
Pan Bian authored
In function sami_paragraph_to_ass(), the return value of av_strdup() is not checked. To avoid potential NULL dereference, the return value should be checked against NULL. Signed-off-by: Pan Bian <bianpan2016@163.com>
-
James Almer authored
Signed-off-by: James Almer <jamrial@gmail.com>
-
wm4 authored
We did this for the sake of the decoder. With the vp9 change, it's not necessary anymore.
-
wm4 authored
webm usually has invisible superframes merged with normal frames. (vpxenc muxes them in this form, which is evidence enough that this is the standard webm packet format. It's rather unclear whether ffmpeg is even allowed to remux them with split packets.) The vp9 decoder needs them to be in separate packets for multithreading to work. Add the BSF to the decoder, so the conversion happens automatically. This contains the important part of fa1749dd, which was apparently skipped in commit d417e95a. This restores Libav API compatibility.
-
James Almer authored
Fixes checkheaders. Signed-off-by: James Almer <jamrial@gmail.com>
-
James Almer authored
Fixes fate-source Signed-off-by: James Almer <jamrial@gmail.com>
-
Karthick J authored
-
Pan Bian authored
In function process_output_surface(), the return value is 0 on the path that av_mallocz() returns a NULL pointer. 0 indicates success, which deviates from the fact. Return "AVERROR(ENOMEM)" instead of "0". Signed-off-by: Pan Bian <bianpan2016@163.com> Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Jeyapal, Karthick authored
-
Jeyapal, Karthick authored
-
Jeyapal, Karthick authored
-
Dale Curtis authored
This leads to signed integer overflow. Signed-off-by: Dale Curtis <dalecurtis@chromium.org> Signed-off-by: James Almer <jamrial@gmail.com>
-
Dale Curtis authored
Otherwise ff_alloc_extradata() just leaks any existing allocated memory. Signed-off-by: Dale Curtis <dalecurtis@chromium.org> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 28 Nov, 2017 11 commits
-
-
James Zern authored
Corpus VBR mode is a variant of standard VBR where the complexity distribution midpoint is passed in rather than calculated for a specific clip or chunk. The valid range is [0, 10000]. 0 (default) uses standard VBR. Signed-off-by: James Zern <jzern@google.com>
-
Carl Eugen Hoyos authored
Fixes a warning: fftools/ffmpeg_opt.c:804:29: warning: assignment discards ‘const’ qualifier from pointer target type
-
Mikhail Mironov authored
Requires AMF headers for at least version 1.4.4.1. Signed-off-by: Mikhail Mironov <mikhail.mironov@amd.com> Signed-off-by: Mark Thompson <sw@jkqxz.net>
-
Jun Zhao authored
Supports only raw NV12 input. Example use: ./vaapi_encode 1920 1080 test.yuv test.h264 Signed-off-by: Jun Zhao <jun.zhao@intel.com> Signed-off-by: Liu, Kaixuan <kaixuan.liu@intel.com> Signed-off-by: Mark Thompson <sw@jkqxz.net>
-
Mark Thompson authored
-
Pan Bian authored
On some failure paths, the error code is not correctly set. Signed-off-by: Pan Bian <bianpan2016@163.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
Pan Bian authored
In function mov_read_custom(), it returns 0 on the path that av_malloc() returns a NULL pointer. 0 indicates success. An error code should be assigned to ret. Signed-off-by: Pan Bian <bianpan2016@163.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
Mark Reid authored
Reviewed-by: Tomas Härdin <tjoppen@acc.umu.se> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
Pan Bian authored
In function ff_mpeg_ref_picture(), it returns 0 on the error path that the return value of av_buffer_ref() is NULL. 0 indicates success, which seems to deviate from the fact. Set ret to AVERROR(ENOMEM) to propagate the error status to the callers. Signed-off-by: Pan Bian <bianpan2016@163.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
Dale Curtis authored
Otherwise ff_alloc_extradata() just leaks any existing allocated memory. Signed-off-by: Dale Curtis <dalecurtis@chromium.org> Reviewed-by: Derek Buitenhuis <derek.buitenhuis@gmail.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
Gyan Doshi authored
The present value name for maximum thickness is 'max' which results in a parse error of any thickness expression containing 'max(val1,val2)'. Value renamed to 'fill'. Tested locally and documented. Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-