- 09 Feb, 2013 1 commit
-
-
Diego Biurrun authored
-
- 08 Feb, 2013 5 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
-
- 07 Feb, 2013 10 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Mans Rullgard authored
The destination is sufficiently aligned for put_pixels here. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Daniel Kang authored
Accidentally prefixed ff_ with cextern. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 06 Feb, 2013 24 commits
-
-
Daniel Kang authored
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
Anton Khirnov authored
-
Anton Khirnov authored
Check slice count and input buffer size before constructing a possibly invalid pointer, not after.
-
Anton Khirnov authored
pp_time is never set for h264
-
Anton Khirnov authored
They serve no useful purpose and wreak all kind of havoc when h264.h is included elsewhere.
-
Anton Khirnov authored
-
Tim Walker authored
They were added to the latest FLAC specification: https://git.xiph.org/?p=flac-website.git;a=commit;h=65c199a2Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Tim Walker authored
This is unnecessary, as ff_flac_set_channel_layout can handle any number of channels. Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Anton Khirnov authored
Do not rely on get_buffer initializing them. Changes yadif tests (off by one in one border pixel), because yadif reads from those uninitialized lines.
-
Anton Khirnov authored
-
Anton Khirnov authored
The FATE sample contains some pixels with value 0, but the palette stored in the file contains only values from 16 up. Because the default and cmdutils get_buffer() initialize the data to 0x80, they appear as gray dots. After this commit they change to black dots, which is probably still incorrect but less visible and doesn't rely on get_buffer() initializing the data.
-
Anton Khirnov authored
CC:libav-stable@libav.org
-
Anton Khirnov authored
CC:libav-stable@libav.org
-
Kostya Shishkov authored
Signed-off-by: Anton Khirnov <anton@khirnov.net> CC:libav-stable@libav.org
-
Kostya Shishkov authored
Duplicate the last one or two chroma lines. Signed-off-by: Anton Khirnov <anton@khirnov.net> CC:libav-stable@libav.org
-
Anton Khirnov authored
CC:libav-stable@libav.org
-
Anton Khirnov authored
The bottom line was invalid before. CC:libav-stable@libav.org
-
Anton Khirnov authored
CC:libav-stable@libav.org
-
Anton Khirnov authored
It's not relying on get_buffer() initializing the frame since 99e36ddd.
-
Anton Khirnov authored
Setting it to zero (instead of 128, as the default get_buffer() does) also produces more correctly-looking output.
-
Anton Khirnov authored
It is used as an array in svq1enc, so this is more correct.
-