- 23 Feb, 2013 28 commits
-
-
Diego Biurrun authored
-
Justin Ruggles authored
-
Justin Ruggles authored
Avoids an option name conflict with libavcodec, which is needed in order to work properly with avconv.
-
Justin Ruggles authored
-
Justin Ruggles authored
-
Justin Ruggles authored
Damaged frames can lead to a mismatch, which can cause a segfault due to using an incorrect channel mapping. CC:libav-stable@libav.org
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Mans Rullgard authored
The enabled hwaccels are listed later anyway. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Diego Biurrun authored
-
Diego Biurrun authored
While we do not use Automake in libav, this allows our config to be used more globally without introducing unwanted breakage.
-
Diego Biurrun authored
The init functions marked as av_cold have to be executed in any case, so there is no gain from trying to mark paths leading to such functions as unlikely.
-
Kostya Shishkov authored
-
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>
-
Anton Khirnov authored
-
Anton Khirnov authored
-
Anton Khirnov authored
CC:libav-stable@libav.org
-
Anton Khirnov authored
Avoids crashes with corrupted files. CC:libav-stable@libav.org
-
Anton Khirnov authored
CC:libav-stable@libav.org
-
Anton Khirnov authored
CC:libav-stable@libav.org
-
Anton Khirnov authored
When byte_run is 0, pixel_countdown is not touched and the loop will run forever. CC:libav-stable@libav.org
-
Anton Khirnov authored
CC:libav-stable@libav.org
-
Anton Khirnov authored
range == 0 happens with corrupted files CC:libav-stable@libav.org
-
Anton Khirnov authored
CC:libav-stable@libav.org
-
Anton Khirnov authored
CC:libav-stable@libav.org
-
- 21 Feb, 2013 1 commit
-
-
Matt Wolenetz authored
This fixes crashes in chromium on win64 on machines with AVX (crashes that apparently aren't triggered by fate). Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 20 Feb, 2013 3 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Vicente Jimenez Aguilar authored
Signed-off-by: Diego Biurrun <diego@biurrun.de>
-
- 19 Feb, 2013 8 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Martin Storsjö authored
This gets rid of a number of warnings about casts discarding qualifiers from the pointer target, present since 7ebfb466. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Ronald S. Bultje authored
Instead, only extend edges on-demand when the motion vector actually crosses the visible decoded area using ff_emulated_edge_mc(). This changes decoding time for cathedral from 8.722sec to 8.706sec, i.e. 0.2% faster overall. More generally (VP8 uses this also), low-motion content gets significant speed improvements, whereas high-motion content tends to decode in approximately the same time. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Ronald S. Bultje authored
Instead, keep them in the bitstream buffer until we read them verbatim, this saves a memcpy() and a subsequent clearing of the target buffer. decode_cabac+decode_mb for a sample file (CAPM3_Sony_D.jsv) goes from 6121.4 to 6095.5 cycles, i.e. 26 cycles faster. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Ronald S. Bultje authored
This allows more transparent mixing of get_bits and whole-byte access without having to touch get_bits internals. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Ronald S. Bultje authored
These functions are mostly H264-specific (the only other user I can spot is bink), and this allows us to special-case some functionality for H264. Also remove the 16-bit-coeff with >8bpp versions (unused) and merge the duplicate 32-bit-coeff for >8bpp (identical). Signed-off-by: Martin Storsjö <martin@martin.st>
-
Ronald S. Bultje authored
These functions do the same thing in 16 bit space and don't need any depth specific clipping. Signed-off-by: Martin Storsjö <martin@martin.st>
-