- 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>
-
- 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>
-
- 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>
-
- 06 Dec, 2015 1 commit
-
-
Anton Khirnov authored
-
- 23 Oct, 2015 1 commit
-
-
Luca Barbato authored
-
- 15 Oct, 2015 1 commit
-
-
Vittorio Giovara authored
-
- 01 Oct, 2015 2 commits
-
-
Derek Buitenhuis authored
When forwarding the frame type information, by default x264 can decide which kind of keyframe output, add an option to force it to output IDR frames in to support use-cases such as preparing the content for segmented streams formats.
-
Yu Xiaolei authored
x264 build 147 adds the native support for NV21. Useful to avoid additional pixel format conversion when encoding from a wide range of capture devices, Android among those. Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 27 Jul, 2015 3 commits
-
-
Vittorio Giovara authored
Express bitfields more simply. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
Convert doxygen to multiline and express bitfields more simply. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This option is extremely codec specific and only a few codecs employ it. Move it to codec private options instead: mpegenc family supports only 3 values, xavs and x264 use 5, and xvid has a different metric entirely. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 20 Jul, 2015 3 commits
-
-
Vittorio Giovara authored
The rationale is that coded_frame was only used to communicate key_frame, pict_type and quality to the caller, as well as a few other random fields, in a non predictable, let alone consistent way. There was agreement that there was no use case for coded_frame, as it is a full-sized AVFrame container used for just 2-3 int-sized properties, which shouldn't even belong into the AVCodecContext in the first place. The appropriate AVPacket flag can be used instead of key_frame, while quality is exported with the new AVPacketSideData quality factor. There is no replacement for the other fields as they were unreliable, mishandled or just not used at all. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This is necessary to preserve the quality information currently exported with coded_frame. Add the new side data to every encoder that needs it, and use it in avconv. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
Allocating coded_frame is what most encoders do anyway, so it makes sense to always allocate and free it in a single place. Moreover a lot of encoders freed the frame with av_freep() instead of the correct API av_frame_free(). This bring uniformity to encoder behaviour and prevents applications from erroneusly accessing this field when not allocated. Additionally this helps isolating encoders that export information with coded_frame, and heavily simplifies its deprecation. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 17 Jul, 2015 1 commit
-
-
Luca Barbato authored
-
- 15 Jun, 2015 1 commit
-
-
Luca Barbato authored
-
- 31 May, 2015 1 commit
-
-
Vittorio Giovara authored
-
- 24 Apr, 2015 1 commit
-
-
Vittorio Giovara authored
This takes care of memory leaks on init error.
-
- 15 Apr, 2015 1 commit
-
-
Luca Barbato authored
-
- 17 Mar, 2015 1 commit
-
-
Carl Eugen Hoyos authored
Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 12 Mar, 2015 1 commit
-
-
Himangi Saraogi authored
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 07 Aug, 2014 1 commit
-
-
Felix Abecassis authored
Column and row frame packing arrangements were inverted. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 22 Jun, 2014 1 commit
-
-
Luca Barbato authored
By default they are set to -1.
-
- 11 Jun, 2014 1 commit
-
-
Luca Barbato authored
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 16 Mar, 2014 1 commit
-
-
Vittorio Giovara authored
-
- 09 Dec, 2013 1 commit
-
-
Vittorio Giovara authored
-
- 16 Nov, 2013 1 commit
-
-
Anton Khirnov authored
-
- 03 Oct, 2013 1 commit
-
-
Diego Biurrun authored
-
- 24 Sep, 2013 1 commit
-
-
Kieran Kunhya authored
Interleaved chroma is x264's native format Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
- 05 Aug, 2013 1 commit
-
-
Luca Barbato authored
As for intra-refresh it is just a commodity.
-
- 21 Jul, 2013 1 commit
-
-
Derek Buitenhuis authored
libx264 has a few data exports which require X264_API_IMPORTS to be defined if we link to libx264 dynamically on Windows. In a similar fashion to how we handle our compat snprintf implementation, if we define it all the time, the compiler will first try and link to __imp_x264_symbol_name, and failing that, as in the case of a static libx264, will attempt to link to the non-prefixed symbol, which has already been pulled in by other x264 functions' object files. Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
-
- 23 Feb, 2013 1 commit
-
-
John Van Sickle authored
This also allows libx264 to modify its i_qfactor value when using the "-tune" setting. Previously it had a static value of 1.25 Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
- 25 Jan, 2013 1 commit
-
-
Gavriloaie Eugen-Andrei authored
It is a shortcut to set all the params using x264_param_parse, makes simpler importing settings from other software using x264.
-
- 15 Jan, 2013 1 commit
-
-
Luca Barbato authored
By default libav sets it to 3/4 while x264 sets it to 9/10. CC: libav-stable@libav.org Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-