- 01 Oct, 2019 1 commit
-
-
Carl Eugen Hoyos authored
Usage of strtok() was removed from x264, see also b02490a4
-
- 24 Sep, 2019 1 commit
-
-
Guo, Yejun authored
Signed-off-by: Guo, Yejun <yejun.guo@intel.com>
-
- 25 Aug, 2019 1 commit
-
-
Carl Eugen Hoyos authored
Missed in c180f0f6
-
- 10 Aug, 2019 3 commits
-
-
Carl Eugen Hoyos authored
Fixes remaining part of ticket #8071 on next version bump.
-
Carl Eugen Hoyos authored
Fixes ticket #8071.
-
Carl Eugen Hoyos authored
-
- 07 Jul, 2019 1 commit
-
-
Mark Thompson authored
Fix the quantisation offset - use the whole range, and don't change the offset size based on bit depth. Iterate the list in reverse order. The first region in the list is the one that applies in the case of overlapping regions.
-
- 10 May, 2019 1 commit
-
-
Jun Zhao authored
perfer avctx->framerate first than use avctx->time_base when setting the frame rate to encoder. 1/time_base is not the average frame rate if the frame rate is not constant. In this case, we need to setting avctx->framerate and avctx->time_base both, but avctx->framerate not equal to 1/(avctx->time_base). Signed-off-by: Jun Zhao <barryjzhao@tencent.com>
-
- 17 Jan, 2019 1 commit
-
-
Guo, Yejun authored
This patch just enables the path from ffmpeg to libx264, the more encoders can be added later. Signed-off-by: Guo, Yejun <yejun.guo@intel.com> Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
-
- 05 Nov, 2018 2 commits
-
-
Martin Storsjö authored
libx264 does have a field for opaque data to pass along with frames through the encoder, but it is a pointer, while the libavcodec reordered_opaque field is an int64_t. Therefore, allocate an array within the libx264 wrapper, where reordered_opaque values in flight are stored, and pass a pointer to this array to libx264. Update the public libavcodec documentation for the AVCodecContext field to explain this usage, and add a codec capability that allows detecting whether an encoder handles this field. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
libx264 does have a field for opaque data to pass along with frames through the encoder, but it is a pointer, while the libavcodec reordered_opaque field is an int64_t. Therefore, allocate an array within the libx264 wrapper, where reordered_opaque values in flight are stored, and pass a pointer to this array to libx264. Update the public libavcodec documentation for the AVCodecContext field to explain this usage, and add a codec capability that allows detecting whether an encoder handles this field. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 24 Oct, 2018 1 commit
-
-
Marton Balint authored
Libx264 uses strtok which is not thread safe. Strtok is used in x264_param_default_preset in param_apply_tune in x264/common/base.c. Therefore the flag must be removed. x264 fixed the issue, once the fix is pushed to stable, an #if can be added to re-enable the flag based on X264_BUILD number. Fixes ticket #7446. Signed-off-by: Marton Balint <cus@passwd.hu>
-
- 07 Aug, 2018 1 commit
-
-
Carl Eugen Hoyos authored
-
- 27 Dec, 2017 1 commit
-
-
Luca Barbato authored
It has native simultaneus 8 and 10 bit support.
-
- 26 Dec, 2017 3 commits
-
-
James Almer authored
This partially reverts a change in behavior introduced in 2a111c99. Signed-off-by: James Almer <jamrial@gmail.com>
-
James Almer authored
x264 now supports multibitdepth builds, with a slightly changed API to request bitdepth during initialization. Reviewed-by: Ricardo Constantino <wiiaboo@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
-
James Almer authored
The x264_bit_depth constant has been removed in newer x264 builds. Signed-off-by: James Almer <jamrial@gmail.com>
-
- 14 Dec, 2017 2 commits
-
-
wm4 authored
Explicitly identify decoder/encoder wrappers with a common name. This saves API users from guessing by the name suffix. For example, they don't have to guess that "h264_qsv" is the h264 QSV implementation, and instead they can just check the AVCodec .codec and .wrapper_name fields. Explicitly mark AVCodec entries that are hardware decoders or most likely hardware decoders with new AV_CODEC_CAPs. The purpose is allowing API users listing hardware decoders in a more generic way. The proposed AVCodecHWConfig does not provide this information fully, because it's concerned with decoder configuration, not information about the fact whether the hardware is used or not. AV_CODEC_CAP_HYBRID exists specifically for QSV, which can have software implementations in case the hardware is not capable. Based on a patch by Philip Langdale <philipl@overt.org>. Merges Libav commit 47687a2f.
-
wm4 authored
Explicitly identify decoder/encoder wrappers with a common name. This saves API users from guessing by the name suffix. For example, they don't have to guess that "h264_qsv" is the h264 QSV implementation, and instead they can just check the AVCodec .codec and .wrapper_name fields. Explicitly mark AVCodec entries that are hardware decoders or most likely hardware decoders with new AV_CODEC_CAPs. The purpose is allowing API users listing hardware decoders in a more generic way. The proposed AVCodecHWConfig does not provide this information fully, because it's concerned with decoder configuration, not information about the fact whether the hardware is used or not. AV_CODEC_CAP_HYBRID exists specifically for QSV, which can have software implementations in case the hardware is not capable. Based on a patch by Philip Langdale <philipl@overt.org>. Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 23 Oct, 2017 1 commit
-
-
James Almer authored
Replaces the now dropped global option. Addresses ticket #6771. Reviewed-by: Paul B Mahol <onemda@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
-
- 23 Mar, 2017 1 commit
-
-
Vittorio Giovara authored
Deprecated in 10/2014 and 07/2015.
-
- 22 Nov, 2016 1 commit
-
-
Timo Rothenpieler authored
Currently, it forces IDR frames for both true and false. Not entirely sure what the original idea behind the tri-state bool option is. Reviewed-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
-
- 14 Sep, 2016 1 commit
-
-
Carl Eugen Hoyos authored
-
- 22 Jul, 2016 1 commit
-
-
Sasi Inguva authored
Signed-off-by: Sasi Inguva <isasi@google.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 23 Jun, 2016 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 19 Jun, 2016 1 commit
-
-
Andrey Turkin authored
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 05 Jun, 2016 1 commit
-
-
Michael Niedermayer authored
This avoids enabling and building the x264rgb encoder when its actually not supported and thus would not work Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 21 Apr, 2016 2 commits
-
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
- 23 Feb, 2016 1 commit
-
-
Vittorio Giovara authored
First check the context, then check internal option. Drop the ! typo. Introduced in 60f0fde3.
-
- 31 Jan, 2016 1 commit
-
-
Vittorio Giovara authored
The private options chromaoffset, sc_threshold, and noise_reduction were set to 0 rather than -1, and were always initializing values in libx264 rather than letting the library use its default. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 28 Jan, 2016 2 commits
-
-
Vittorio Giovara authored
The private options chromaoffset, sc_threshold, and noise_reduction were set to 0 rather than -1, and were always initializing values in libx264 rather than letting the library use its default. Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
Michael Niedermayer authored
After the merge the default threshold was unconditionally overwritten A similar fix was written by Vittorio Giovara, but i didnt see that before i wrote this and it also doesnt apply cleanly Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 27 Jan, 2016 1 commit
-
-
Derek Buitenhuis authored
Libav, for some reason, merged this as a public API function. This will aid in future merges. A define is left for backwards compat, just in case some person used it, since it is in a public header. Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
-
- 21 Jan, 2016 4 commits
-
-
Vittorio Giovara authored
This option is only used by mpegvideoenc, x264, xavs, and vpx. It is a very codec-specific option, so deprecate the global variant. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This option is only used by mpegvideoenc, x264, and xavs. It is a very codec-specific option, so deprecate the global variant. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This option is only used by x264 and xavs. It is a very codec-specific option, so deprecate the global variant. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
The b_frame_strategy option is only used by mpegvideoenc, qsv, x264, and xavs, while b_sensitivity is only used by mpegvideoenc. These are very codec-specific options, so deprecate the global variants. Set proper limits to the maximum allowed values. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 10 Jan, 2016 1 commit
-
-
Carl Eugen Hoyos authored
Fixes ticket #5142.
-
- 07 Dec, 2015 1 commit
-
-
Vittorio Giovara authored
Most option values are simply unused or ignored and in practice the majory of codecs only need to check whether to enable rle or not. Add appropriate codec private options which better expose the allowed features. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-