- 27 Feb, 2013 1 commit
-
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 24 Feb, 2013 2 commits
-
-
Paul B Mahol authored
Signed-off-by:
Paul B Mahol <onemda@gmail.com>
-
Paul B Mahol authored
Signed-off-by:
Paul B Mahol <onemda@gmail.com>
-
- 22 Feb, 2013 2 commits
-
-
Clément Bœsch authored
-
Stefano Sabatini authored
"12:34" is now valid syntax.
-
- 20 Feb, 2013 2 commits
-
-
Clément Bœsch authored
-
u-bo1b@0w.se authored
The new code is also faster and more robust. As for the performance: old decoder + conversion to rgb: fps = 2618 old decoder, without converting to rgb: fps = 4012 new decoder, producing rgb: fps = 4502 Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 17 Feb, 2013 1 commit
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 15 Feb, 2013 1 commit
-
-
Anton Khirnov authored
Some changes in the border pixels, visually indistinguishable.
-
- 14 Feb, 2013 1 commit
-
-
James Almer authored
Signed-off-by:
James Almer <jamrial@gmail.com> Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 13 Feb, 2013 1 commit
-
-
Vignesh Venkatasubramanian authored
Matroska specification lists support for BlockAdditional element which is not supported by ffmpeg's matroska parser. This patch adds grammar definitions for parsing that element (and few other related elements) and then puts the data in AVPacket.side_data with new AVPacketSideDataType AV_PKT_DATA_MATROSKA_BLOCKADDITIONAL. Signed-off-by:
Vignesh Venkatasubramanian <vigneshv@google.com> Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 07 Feb, 2013 1 commit
-
-
Michael Niedermayer authored
This replaces a large number of checks for the second field by fixing the pointers when they are setup This should also fix I/BI field pictures Changes checksums for vc1_sa10143, the file becomes slightly closer to what the reference decoder outputs Based on "vc1dec: the second field is written wrong to the picture" by Sebastian Sandberg <sebastiand.sandberg@gmail.com> Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 06 Feb, 2013 8 commits
-
-
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
-
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
Setting it to zero (instead of 128, as the default get_buffer() does) also produces more correctly-looking output.
-
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.
-
- 24 Jan, 2013 1 commit
-
-
Stefano Sabatini authored
Add support to an if/else construct, simplify logic in expressions.
-
- 20 Jan, 2013 1 commit
-
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 17 Jan, 2013 1 commit
-
-
Luca Barbato authored
-
- 15 Jan, 2013 2 commits
-
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 12 Jan, 2013 1 commit
-
-
Diego Biurrun authored
Also rename the test to reflect that the video track is Theora, not VP3.
-
- 11 Jan, 2013 2 commits
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Clément Bœsch authored
-
- 10 Jan, 2013 1 commit
-
-
Diego Biurrun authored
-
- 09 Jan, 2013 1 commit
-
-
Justin Ruggles authored
Add some additional checks for EOF and print error messages on an incomplete header or packet. FATE reference updated for id-cin-video due to the demuxer no longer returning a partial video packet at EOF.
-
- 08 Jan, 2013 1 commit
-
-
Paul B Mahol authored
Signed-off-by:
Paul B Mahol <onemda@gmail.com>
-
- 03 Jan, 2013 2 commits
-
-
Clément Bœsch authored
The FATE test is updated because the line breaks in the dialogue rectangles are now proper CRLF.
-
Clément Bœsch authored
The data does not contain timing or trailing line breaks anymore. In addition to being less idiotic, it is consistent with other codecs and thus allows more switches between formats and codecs. It also fixes the issue of the trailing line returns being simple \n instead of CRLF in the ASS rectangle dialogue (this is the reason of the FATE update).
-
- 02 Jan, 2013 3 commits
-
-
Clément Bœsch authored
The flags are necessary for the auto inserted scaler (because the overlay filter needs an alpha channel for the overlay surface).
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Nicolas George authored
-
- 01 Jan, 2013 2 commits
-
-
Nicolas George authored
They were two very short files that cover ffmpeg-specific features.
-
Paul B Mahol authored
Signed-off-by:
Paul B Mahol <onemda@gmail.com>
-
- 30 Dec, 2012 2 commits
-
-
Clément Bœsch authored
Current MicroDVD AVPackets contain timing information and trailing line breaks. The data is now only composed of the markup data. Doing this consistently between text subtitles decoders allows to use different codec for various formats. For instance, MicroDVD markup is sometimes found in some VPlayer files. Also, generally speaking, the subtitles text decoders have no use of these timings (and they must not use them since it would break any user timing adjustment). Technically, this is a major ABI break. In practice, a mismatching lavf/lavc will now error out for MicroDVD decoding. Supporting both formats requires unnecessary complex and fragile code. FATE needs update because line breaks in the ASS file were "\n" (because that's what is used in the original file). ASS format expect "\r\n" line breaks; this commit fixes this issue. Also note that this "\r\n" trailing need to be moved at some point from the decoders to the ASS muxer.
-
Clément Bœsch authored
-