- 20 Jul, 2016 4 commits
-
-
Anton Khirnov authored
The current code will ignore the init_get_bits() failure and do an invalid read from the uninitialized GetBitContext. Found-By: Jan Ruge <jan.s.ruge@gmail.com> Bug-Id: 952
-
Anton Khirnov authored
It does not break anything currently, but should not be done anyway.
-
Hendrik Leppkes authored
Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Hendrik Leppkes authored
This fixes retrieving a valid profile for many of the FATE conformance samples, allowing them to be properly decoded by the HWAccel after adding a profile check. Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
- 18 Jul, 2016 6 commits
-
-
James Almer authored
Originally written by Pierre Edouard Lepere <pierre-edouard.lepere@insa-rennes.fr>. Integrated to Libav by Josh de Kock <josh@itanimul.li>. Signed-off-by: Alexandra Hájková <alexandra@khirnov.net>
-
Mickaël Raulet authored
Integrated to libav by Josh de Kock <josh@itanimul.li>. Signed-off-by: Alexandra Hájková <alexandra@khirnov.net>
-
Mickaël Raulet authored
Integrated to Libav by Josh de Kock <josh@itanimul.li>. Signed-off-by: Alexandra Hájková <alexandra@khirnov.net>
-
Mickaël Raulet authored
Integrated to Libav by Josh de Kock <josh@itanimul.li>. Signed-off-by: Alexandra Hájková <alexandra@khirnov.net>
-
Alexandra Hájková authored
Based on patch 250430bf by Mickaël Raulet <mraulet@insa-rennes.fr>, integrated to Libav by Josh de Kock <josh@itanimul.li>. Signed-off-by: Alexandra Hájková <alexandra@khirnov.net>
-
James Almer authored
Integration to Libav by Josh de Kock <josh@itanimul.li>. Signed-off-by: Alexandra Hájková <alexandra@khirnov.net>
-
- 17 Jul, 2016 3 commits
-
-
Martin Storsjö authored
These bits are set by exceptions in NEON instructions. Also print the differing bits when FPSCR is clobbered, and use bic instead of lsl, for clearing the topmost bits. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Janne Grunau authored
Fixes AS error on non NEON builds introduced in 71a04721. Also set the fpu directly to vfp in checkasm.S to cause build errors on NEON builds.
-
Martin Storsjö authored
Each const block needs to be terminated by one endconst invocation so either call endconst after each, or just declare plain labels to the later strings. This fixes errors such as this, on some binutils versions: checkasm.S:38: Error: Macro `endconst' was already defined Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 16 Jul, 2016 4 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
They are internal symbols that should not be exported. based on a patch by Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com> Signed-off-by: Diego Biurrun <diego@biurrun.de>
-
Andreas Cadhalpun authored
It is an internal swscale symbol and thus should not be exported. Signed-off-by: Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com> Signed-off-by: Diego Biurrun <diego@biurrun.de>
-
Janne Grunau authored
-
- 15 Jul, 2016 13 commits
-
-
Hendrik Leppkes authored
Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Anton Khirnov authored
-
Anton Khirnov authored
-
Anton Khirnov authored
Since we only know whether a NAL unit corresponds to a new field after parsing the slice header, this requires reorganizing the calls to slice parsing, per-slice/field/frame init and actual decoding. In the previous code, the function for slice header decoding also immediately started a new field/frame as necessary, so any slices already queued for decoding would no longer be decodable. After this patch, we first parse the slice header, and if we determine that a new field needs to be started we decode all the queued slices.
-
Anton Khirnov authored
This function's purpose is not very well defined. Currently it does two (only marginally related) things: selecting the next output frame and calling ff_thread_finish_setup() for frame threading. The first of those more properly belongs under field_start(), while the second can be called directly from decode_nal_units().
-
Anton Khirnov authored
-
Anton Khirnov authored
-
Anton Khirnov authored
-
Martin Storsjö authored
Also set FF_CODEC_CAP_INIT_THREADSAFE while adding internal capabilities. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Previously they returned the default AVERROR_UNKNOWN. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Matthieu Bouron authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 13 Jul, 2016 7 commits
-
-
Vittorio Giovara authored
The input packet is already unref'd by the calling function.
-
Vittorio Giovara authored
See 17c99b61. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
Janne Grunau authored
The stack used by checkasm_checked_call_vfp was a multiple of 4 when the checked function is called. AAPCS requires a double word (8 byte) aligned stack public interfaces. Since both calls are public interfaces the stack is misaligned when the checked is called. Might fix the SIGBUS error in the armv7-linux-clang-3.7 fate config.
-
Janne Grunau authored
Fixes "Use of uninitialised value" valgrind warnings in checkasm.
-
Janne Grunau authored
Fixes a regression in ca2f19b9 with some mov/mp4 files. The files have several NAL units in the supposed single NAL unit after the size field. Annex B start code prefixes are used to separate them. The first NAL unit is correctly parsed but the buffer does not point to the next size field. Instead semi random data (it seems to be the rbsp_stop_one_bit and the start code prefix) is then parsed as length and will exceed the remaining length of the buffer. Patch based on the code in h264's decode_nal_units() and a similar patch by Hendrik Leppkes in FFmpeg (a9bb4cf8). Bug-Id: ffmpeg/trac5529 Reported-By: Vittorio Giovara
-
- 11 Jul, 2016 2 commits
-
-
Anton Khirnov authored
Currently, SPS.mb_height is actually what the spec calls PicHeightInMapUnits, which is half the frame height when interlacing is allowed. Calling this 'mb_height' is quite confusing, and there are at least two associated bugs where this field is treated as the actual frame height - in the h264 parser and in the code computing maximum reordering buffer size for a given level. Fix those issues (and avoid possible future ones) by exporting the real frame height in this field.
-
Steve Lhomme authored
also fixes a deadlock found by Денис Кулаков <kudesnik33ra@gmail.com> Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
- 10 Jul, 2016 1 commit
-
-
Martin Storsjö authored
This comment isn't true, the height can be different from the width for these functions (which is why the height is passed as a parameter to them). Signed-off-by: Martin Storsjö <martin@martin.st>
-