- 26 Jan, 2014 2 commits
-
-
Loren Merritt authored
Work around Yasm's inefficiency with handling large numbers of variables in the global scope. Signed-off-by:
Diego Biurrun <diego@biurrun.de>
-
Michael Niedermayer authored
Without this a developer would have to add a include every time he wants to benchmark some code, this is a moderate inconvenience. This reverts the specific hunk from fb0c9d41Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 25 Jan, 2014 1 commit
-
-
Janne Grunau authored
Added libavutil/timer.h include to all files with {START,STOP}_TIMER.
-
- 24 Jan, 2014 1 commit
-
-
João Bernardo authored
Signed-off-by:
João Bernardo Oliveira <jbvsmo@gmail.com> Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 19 Jan, 2014 1 commit
-
-
Nicolas George authored
Add a function to create a rational and macros for common values.
-
- 18 Jan, 2014 1 commit
-
-
Loren Merritt authored
Work around yasm's inefficiency with handling large numbers of variables in the global scope.
-
- 17 Jan, 2014 2 commits
-
-
Luca Barbato authored
-
Luca Barbato authored
-
- 15 Jan, 2014 2 commits
-
-
Janne Grunau authored
-
Janne Grunau authored
NEON and VFP are currently mandatory for all ARMv8 profiles. Both are handled as extensions as far as cpuflags are concerned. This is consistent with handling x86_64 which always has SSE2, but still handles it as an extension.
-
- 14 Jan, 2014 1 commit
-
-
Janne Grunau authored
Signed-off-by:
Janne Grunau <janne-libav@jannau.net>
-
- 10 Jan, 2014 1 commit
-
-
Martin Storsjö authored
This is pretty much based on the same test for XMM registers. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 09 Jan, 2014 1 commit
-
-
Vittorio Giovara authored
-
- 07 Jan, 2014 1 commit
-
-
Martin Storsjö authored
The function macro always sets .align 2 before declaring the function label (since 5c5e1ea3) and always sets the section to .text (since 278caa6a). The .align 5 before certain functions, added in fc252eba, were added before .text and .align were added to the function macro and thus became useless/unused when the function macro got them. This restores the original intention, to align the loop entry points. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 06 Jan, 2014 1 commit
-
-
Michael Niedermayer authored
The new code is faster and reuses the previous state in case of multiple calls. The previous code could easily end up in near-infinite loops, if the difference between two clock() calls never was larger than 1. This makes fate-parseutils finish in finite time when run in wine, if CryptGenRandom isn't available (which e.g. isn't available if targeting Windows RT/metro). Patch originally by Michael Niedermayer but with some modifications by Martin Storsjö. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 05 Jan, 2014 2 commits
-
-
Tim Walker authored
Includes a libavcodec utility function to update a frame's side data.
-
Tim Walker authored
-
- 04 Jan, 2014 2 commits
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 03 Jan, 2014 2 commits
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Anton Khirnov authored
It is a public function, it must not assert on its parameters.
-
- 29 Dec, 2013 1 commit
-
-
Luca Barbato authored
And remove all the circular inclusions of avutil.h while at it.
-
- 28 Dec, 2013 1 commit
-
-
Michael Niedermayer authored
This matches what avcodec uses Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 26 Dec, 2013 6 commits
-
-
Diego Biurrun authored
This is a more sensible place for these macros.
-
Stefano Sabatini authored
The constant may change in libavutil but the library may be compiled against an older version, thus rejecting a value which is otherwise supported by the new libavutil. INT_MAX is used here to denote the max allowed value for a sample format. The opt-test code is changed to provide a valid reference example.
-
Stefano Sabatini authored
The constant may change in libavutil but the library may be compiled against an older version, thus rejecting a value which is otherwise supported by the new libavutil. INT_MAX is used here to denote the max allowed value for a pixel format. The opt-test code is changed to provide a valid reference example.
-
Stefano Sabatini authored
Previously when setting a pixel/sample format as a string range checks were not performed. This is consistent with the av_opt_set_pixel/sample_fmt() interface.
-
Stefano Sabatini authored
Simplify incoming patch.
-
Stefano Sabatini authored
In particular, allow to reject undefined values. Previously the code was only accepting values in the range -1 .. NB_FORMATS-1.
-
- 24 Dec, 2013 1 commit
-
-
Diego Biurrun authored
-
- 22 Dec, 2013 3 commits
-
-
Tim Walker authored
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Ivan Kalvachev authored
Signed-off-by:
Ivan Kalvachev <ikalvachev@gmail.com> Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 20 Dec, 2013 1 commit
-
-
Diego Biurrun authored
Also fix the #endif comment in a few places and #include config.h to avoid assuming it is #included implicitly.
-
- 18 Dec, 2013 1 commit
-
-
Michael Niedermayer authored
Revert "Merge commit '3bc2e89c'" (Bump libavutil major version to account for the LLS API/ABI changes.) This reverts commit 792845e4, reversing changes made to 1d6666a6. Bumping libavutil requires all libraries that use libavutil to have their major version bumped (yes breakage has been confirmed this is not a hypotheses) One case of breakage is due to new types being added to AVOptions and applications that linked to old libavutil and libswresample then trying to use old libavutil (its soname changed so the old isnt updated) and new swresample (its soame didnt change so it is updated) the new swresample contains AVOption types that the old libavutil doesnt know of thus the application attempting to access these avoptions fails AVOptions are used by all libs so the issue can potentially happen with any other lib, libswresample was just the first that showed the problem ive not checked if the other libs are affected currently by the same issue or not Also in addition to AVOptions, AVFrames are also defined in libavutil, bumping it without all libs that use AVFrames could lead to serious inconsistencies when 2 libs/app end up using 2 different libavutils The alternative of bumping all is still possible after this revert, if it turns out to be the preferred solution
-
- 17 Dec, 2013 1 commit
-
-
Vittorio Giovara authored
-
- 16 Dec, 2013 2 commits
-
-
Stefano Sabatini authored
-
Diego Biurrun authored
It was deprecated over two years ago.
-
- 14 Dec, 2013 1 commit
-
-
Reinhard Tartler authored
Commit 41578f70 changed the LLS API, which was called from libavcodec. Thus using an old libavcodec with a new libavutil will break. All scheduled API changes are deferred to the next bump.
-
- 13 Dec, 2013 1 commit
-
-
Luca Barbato authored
Uniform the style and eliminate a warning on newer doxygen version..
-