- 11 Feb, 2020 1 commit
-
-
Wonkap Jang authored
In order for rate control to correctly allocate bitrate to each temporal layer, correct temporal layer id has to be set to each frame. This commit provides the ability to set correct temporal layer id for each frame. Signed-off-by: James Zern <jzern@google.com>
-
- 03 Feb, 2020 1 commit
-
-
Wonkap Jang authored
This commit reuses the configuration options for VP8 that enables temporal scalability for VP9. It also adds a way to enable three preset temporal structures (refer to the documentation for more detail) that can be used in offline encoding. Signed-off-by: James Zern <jzern@google.com>
-
- 07 Jan, 2020 1 commit
-
-
James Zern authored
Reviewed-by: James Almer <jamrial@gmail.com> Signed-off-by: James Zern <jzern@google.com>
-
- 01 Jan, 2020 1 commit
-
-
Marton Balint authored
Signed-off-by: Marton Balint <cus@passwd.hu>
-
- 09 Nov, 2019 1 commit
-
-
James Zern authored
predicition -> prediction
-
- 06 Nov, 2019 2 commits
-
-
Marton Balint authored
Signed-off-by: Marton Balint <cus@passwd.hu> Signed-off-by: James Zern <jzern@google.com>
-
Marton Balint authored
Signed-off-by: Marton Balint <cus@passwd.hu> Signed-off-by: James Zern <jzern@google.com>
-
- 08 Oct, 2019 1 commit
-
-
elliottk authored
Current default is 200kbps, which produces inconsistent results (too high for low-res, too low for hi-res). Use CRF instead, which will adapt. Affects VP9. Also have VP8 use a default bitrate of 256kbps. Signed-off-by: James Zern <jzern@google.com>
-
- 20 Sep, 2019 1 commit
-
-
Guo, Yejun authored
example command line to verify it: ./ffmpeg -i input.stream -vf addroi=0:0:iw/3:ih/3:-0.8 -c:v libvpx -b:v 2M tmp.webm Signed-off-by: Guo, Yejun <yejun.guo@intel.com> Signed-off-by: James Zern <jzern@google.com>
-
- 12 May, 2019 1 commit
-
-
Jun Zhao authored
Redundant condition: '!A || B' is equivalent to '!A || (A && B)' but more clearly. Signed-off-by: Jun Zhao <barryjzhao@tencent.com>
-
- 24 Dec, 2018 1 commit
-
-
Rene Claus authored
This commit adds configuration options to libvpxenc.c that can be used to tune the sharpness parameter for VP8 and VP9. Signed-off-by: Rene Claus <rclaus@google.com> Signed-off-by: James Zern <jzern@google.com>
-
- 19 Nov, 2018 2 commits
-
-
James Zern authored
Signed-off-by: James Zern <jzern@google.com>
-
Ard Oerlemans authored
This commit adds configuration options to libvpxenc.c that can be used to enable VP8 temporal scalability. It also adds a way to programmatically set the per-frame encoding flags which can be used to control usage and updates of reference frames while encoding with temporal scalability enabled. Signed-off-by: James Zern <jzern@google.com>
-
- 16 Nov, 2018 1 commit
-
-
Chirag Lathia authored
Signed-off-by: Chirag Lathia <clathia@google.com> Signed-off-by: James Almer <jamrial@gmail.com>
-
- 10 Nov, 2018 2 commits
-
-
James Zern authored
vp9 now supports [0, 6] Reviewed-by: James Almer <jamrial@gmail.com> Signed-off-by: James Zern <jzern@google.com>
-
James Zern authored
enables temporal dependency model Signed-off-by: James Zern <jzern@google.com>
-
- 21 May, 2018 1 commit
-
-
James Almer authored
The libvpx doxy says that a value of 0 for the g_threads field is equivalent to a value of 1, whereas for avctx->thread_count it means the maximum amount of threads possible for the host system. Use av_cpu_count() to get the correct thread count when auto threads is requested. Reviewed-by: James Zern <jzern@google.com> 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>
-
- 28 Nov, 2017 1 commit
-
-
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>
-
- 21 Nov, 2017 1 commit
-
-
James Zern authored
Reviewed-by: James Almer <jamrial@gmail.com> Signed-off-by: James Zern <jzern@google.com>
-
- 17 Nov, 2017 1 commit
-
-
James Zern authored
this matches the vpxenc parameter Signed-off-by: James Zern <jzern@google.com>
-
- 29 Apr, 2017 1 commit
-
-
James Zern authored
this was added in 1.6.0 Reviewed-by: Ronald S. Bultje <rsbultje@gmail.com> Signed-off-by: James Zern <jzern@google.com>
-
- 23 Mar, 2017 1 commit
-
-
Vittorio Giovara authored
Deprecated in 10/2014 and 07/2015.
-
- 06 Mar, 2017 1 commit
-
-
Kagami Hiiragi authored
Signed-off-by: James Zern <jzern@google.com>
-
- 13 Dec, 2016 1 commit
-
-
Alex Converse authored
Fixes "Failed to set VP9E_GET_LEVEL codec control: Codec does not implement requested capability" log messages on VP8 encodes.
-
- 28 Nov, 2016 1 commit
-
-
Alex Converse authored
Report the actual level of the encoded output if a level is targeted or the level is passively tracked with a target of 0.
-
- 22 Nov, 2016 1 commit
-
-
Alex Converse authored
Levels are specified at https://www.webmproject.org/vp9/levels/
-
- 22 Oct, 2016 1 commit
-
-
Kagami Hiiragi authored
vp9_cx_iface actually allows values in range [0..2]. This fixes ticket #5894. Signed-off-by: Kagami Hiiragi <kagami@genshiken.org> Signed-off-by: James Zern <jzern@google.com>
-
- 17 Sep, 2016 1 commit
-
-
Carl Eugen Hoyos authored
Fixes ticket #5815.
-
- 23 Jul, 2016 1 commit
-
-
Luca Barbato authored
The range field has been introduced in version 1.6.0
-
- 22 Jul, 2016 1 commit
-
-
James Zern authored
+ the context struct Reviewed-by: Michael Niedermayer <michael@niedermayer.cc> Signed-off-by: James Zern <jzern@google.com>
-
- 13 Jul, 2016 1 commit
-
-
Vignesh Venkatasubramanian authored
Chrome canary now supports decoding of VP9 streams with alpha channel [1]. Add support to ffmpeg for creating such files. [1] https://codereview.chromium.org/2096813002/Reviewed-by: James Zern <jzern@google.com> Signed-off-by: Vignesh Venkatasubramanian <vigneshv@google.com>
-
- 23 Feb, 2016 1 commit
-
-
James Zern authored
with older versions of libvpx since: 432be636 lavc/libvpx: Fix support for RGB colorspace. Reviewed-by: James Almer <jamrial@gmail.com> Signed-off-by: James Zern <jzern@google.com>
-
- 19 Feb, 2016 3 commits
-
-
Carl Eugen Hoyos authored
-
Carl Eugen Hoyos authored
Reported and tested by Nicolas George. Fixes ticket #5249.
-
Carl Eugen Hoyos authored
-
- 07 Feb, 2016 1 commit
-
-
Timothy Gu authored
-
- 21 Jan, 2016 2 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
These options are only used by mpegvideoenc and vpx. They are very codec-specific options, so deprecate the global variants. Add an allowed value to the private options for frame_skip_cmp which seems to have been forgotten, but perfectly working. The libvpx frame dropping feature uses one of such option (frame_skip_threshold) without the other three. For this reason rename the option to something more consistent with the other libvpx variables. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-