- 28 Aug, 2015 1 commit
-
-
Henrik Gramner authored
Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
- 26 Aug, 2015 3 commits
-
-
Luca Barbato authored
Reported-By: zehan@magicpony.technology
-
Timothy Gu authored
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
Timothy Gu authored
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 25 Aug, 2015 3 commits
-
-
Luca Barbato authored
And update the preference for the newer codecs now that the libraries seem stable and widespread enough. Bug-Id: 695 Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
Right now only version 2 and version 3 are supported. Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 24 Aug, 2015 7 commits
-
-
Vittorio Giovara authored
1440x1080@8 progressive (1259) and interlaced (1260). Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
-
Vittorio Giovara authored
This helps in finding duplicates.
-
Vittorio Giovara authored
-
Vittorio Giovara authored
This helps in finding duplicates.
-
Vittorio Giovara authored
-
Vittorio Giovara authored
Use a comment to list the reused tables, since it's more flexible than a table name to keep information like this. The list will expand in later commits.
-
- 23 Aug, 2015 3 commits
-
-
Luca Barbato authored
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
Bug-Id: CID 1308153
-
Luca Barbato authored
Avoid a division by zero. Bug-Id: CID 1257655
-
- 21 Aug, 2015 5 commits
-
-
Luca Barbato authored
Broken in f9ab4fe1
-
John Högberg authored
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
If the candidate does not have alpha and the source does have alpha report the loss of alpha. CC: libav-stable@libav.org
-
Anton Khirnov authored
put_weighted_pred_avg should be put_unweighted_pred_avg, there is no weighting there.
-
Anton Khirnov authored
-
- 20 Aug, 2015 3 commits
-
-
Henrik Gramner authored
Now we no longer have to rely on function pointers intentionally declared without specified argument types. This makes it easier to support functions with floating point parameters or return values as well as functions returning 64-bit values on 32-bit architectures. It also avoids having to explicitly cast strides to ptrdiff_t for example. Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Henrik Gramner authored
If the return value doesn't fit in a single register rdx/edx can in some cases be used in addition to rax/eax. Doesn't affect any of the existing checkasm tests but might be useful later. Also comment the relevant code a bit better. Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Janne Grunau authored
-
- 16 Aug, 2015 4 commits
-
-
Alexandra Hájková authored
also do not return the error code but just break reading metadata object in the case of the aspect ratio reading failure Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
Alexandra Hájková authored
Test the demuxer for the case when the replicated data length in a sample is 0. Sample-ID: https://samples.libav.org/mplayer-bugs/bug821/bug821-2.asfSigned-off-by: Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
Do not risk mixing different timebases. CC: libav-stable@libav.org Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
Federico Tomassetti authored
CC: libav-stable@libav.org
-
- 15 Aug, 2015 4 commits
-
-
Martin Storsjö authored
Previously most of the error paths leaked. Also add FF_CODEC_CAP_INIT_THREADSAFE while adding caps_internal; this decoder wrapper doesn't have any static data that is initialized. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
For ADTS streams, the output format (number of channels, frame size) can change at any point (with the latest version of fdk-aac, the decoder seems to change format after a handful of frames, not outputting the right format immediately, for cases that worked fine with the earlier version of the lib). Previously, the decoder decoded straight into the output frame once the number of channels and frame size was known. This obviously does not work if the number of channels or frame size changes. The alternative would be to allocate the AVFrame with the maximum number of channels and frame size, and change them afterward decoding into it, but that may cause confusion to users e.g. of the get_buffer callback. This solution should be more robust. CC: libav-stable@libav.org Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
In the latest version of fdk-aac, the decoder can output up to 8 channels; take this into account when preallocating buffers that need to fit the output from any packet. CC: libav-stable@libav.org Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Don't try to detect the float ABI by checking at the toolchain name or by trying to assemble and link files with eabi_attributes. This fixes the float ABI detection when building using clang with -fembed-bitcode, where the current eabi_attributes check accidentally passes. This issue was pointed out by James Howe <james.howe@hp.com>. CC: libav-stable@libav.org Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 13 Aug, 2015 1 commit
-
-
Henrik Gramner authored
Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
- 12 Aug, 2015 1 commit
-
-
Martin Storsjö authored
The double meaning of the faststart flag (moving a moov atom to the start of files, making them streamable, for non-fragmented files, vs inserting a global sidx index at the start of files for fragmented files) is confusing - see 40ed1cbf for explanation of its origins. Since the second meaning of the flag hasn't been part of any libav release yet, just rename it to get rid of the confusion without any extra deprecation (which wouldn't get rid of the potential confusion, of users adding -movflags faststart even for fragmented files, where it isn't needed for making them "streamable"). This gets back the old behaviour, where -movflags faststart doesn't have any effect for fragmented files. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 11 Aug, 2015 5 commits
-
-
Henrik Gramner authored
The .text section is already 16-byte aligned by default on all supported platforms so `SECTION_TEXT` isn't any different from `SECTION .text`. Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Henrik Gramner authored
The bug was fixed in 1.3.0, so only perform the workaround in earlier versions. Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Christophe Gisquet authored
Signed-off-by: Henrik Gramner <henrik@gramner.com> Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Anton Mitrofanov authored
Signed-off-by: Henrik Gramner <henrik@gramner.com> Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Henrik Gramner authored
Change ALLOC_STACK to always align the stack before allocating stack space for consistency. Previously alignment would occur either before or after allocating stack space depending on whether manual alignment was required or not. Signed-off-by: Anton Khirnov <anton@khirnov.net>
-