- 28 Feb, 2012 9 commits
-
-
Ronald S. Bultje authored
They cause various issues further down in demuxing. Found-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind CC: libav-stable@libav.org
-
Alex Converse authored
Found-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind
-
Ronald S. Bultje authored
Found-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind CC: libav-stable@libav.org
-
Diego Biurrun authored
-
Ronald S. Bultje authored
Splits at borders of cells are invalid, since it leaves one of the cells with a width/height of zero. Also, propagate errors on buffer allocation failures, so we don't continue decoding (which crashes). Found-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind CC: libav-stable@libav.org
-
Diego Biurrun authored
-
Luca Barbato authored
Provide a way to wrap around the segment index so pseudostreaming live through a web server and html5 browser is simpler. Also ensure that 0 (disable) is a valid value across the options providing wrap around.
-
Luca Barbato authored
-
Alex Converse authored
-
- 27 Feb, 2012 12 commits
-
-
Diego Biurrun authored
-
Derek Buitenhuis authored
WavPack has a comprehensive test suite, and a bunch of corner cases. Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com> Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>
-
Ronald S. Bultje authored
-
Michael Niedermayer authored
The index validation identifies these indexes as broken. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
By validating the index entries while reading, we don't need to seek at startup to validate the entries. If the error in the index entries is not pointing to (our definition of) the start of packets, and there is an index entry pointing at some of the first packets after the metadata, the invalid index can be discarded almost immediately. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Tommy Winther authored
This returns 200 OK for OPTIONS requests and 501 Not Implemented for all other requests. Even though this doesn't do much actual handling of the requests, it makes the code properly identify server requests as such, instead of interpreting it as a reply to the client's request as it did before. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Justin Ruggles authored
For encoding, AVCodecContext.frame_size is the number of input samples to send to the encoder and does not necessarily correspond directly to the timestamps of the output packets.
-
Justin Ruggles authored
-
Justin Ruggles authored
-
Anton Khirnov authored
-
Anton Khirnov authored
Put related fields together, move the important ones closer to the beginning, try to eliminate holes.
-
Anton Khirnov authored
Put related fields together, move the important ones closer to the beginning, try to eliminate holes.
-
- 26 Feb, 2012 11 commits
-
-
Anton Khirnov authored
Neither of those is guaranteed to be connected to framerate in any way (if it even exists). Fixes bug 56.
-
Anton Khirnov authored
-
Reinhard Tartler authored
Because in contrast to the decoder, the parser does not setup low_delay. The code in parse_nal_units would always end up setting has_b_frames to "1", except when stream is explicitly marked as low delay. Since the parser itself would create 'extradata', simply reopening the parser would cause this. This happens for instance in estimate_timings_from_pts(), which causes the parser to be reopened on the same stream. This fixes Libav #22 and FFmpeg (trac) #360 CC: libav-stable@libav.org Based on a patch by Reimar Döffinger <Reimar.Doeffinger@gmx.de> (commit 31ac0ac2) Comments and description adapted by Reinhard Tartler. Signed-off-by: Reinhard Tartler <siretart@tauware.de>
-
Anton Khirnov authored
It's not supposed to be set outside of lavc.
-
Anton Khirnov authored
r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a
-
Anton Khirnov authored
-
Anton Khirnov authored
No functional changes, just make it more readable.
-
Anton Khirnov authored
No changes in the test results.
-
Paul B Mahol authored
Signed-off-by: Paul B Mahol <onemda@gmail.com> Signed-off-by: Justin Ruggles <justin.ruggles@gmail.com>
-
Paul B Mahol authored
Signed-off-by: Paul B Mahol <onemda@gmail.com> Signed-off-by: Justin Ruggles <justin.ruggles@gmail.com>
-
Paul B Mahol authored
Signed-off-by: Paul B Mahol <onemda@gmail.com> Signed-off-by: Justin Ruggles <justin.ruggles@gmail.com>
-
- 25 Feb, 2012 8 commits
-
-
Tim Walker authored
Signed-off-by: Justin Ruggles <justin.ruggles@gmail.com>
-
Justin Ruggles authored
-
Justin Ruggles authored
-
Justin Ruggles authored
-
Justin Ruggles authored
It is not allowed to change mid-stream like it does currently. Instead we need to buffer the first 8 frames before returning them as a single packet, then only return single frame packets after that.
-
Justin Ruggles authored
-
Justin Ruggles authored
-
Justin Ruggles authored
-