- 02 Apr, 2014 1 commit
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 19 Mar, 2014 1 commit
-
-
Carl Eugen Hoyos authored
-
- 26 Dec, 2013 1 commit
-
-
Diego Biurrun authored
This is a more sensible place for these macros.
-
- 06 Oct, 2013 1 commit
-
-
Michael Niedermayer authored
Suggested-by: Ronald S. Bultje Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 15 Aug, 2013 1 commit
-
-
Michael Niedermayer authored
This allows specifying more dither algorithms without using up flags and without ambiguities. Also initialize the new field based on the flags and use it. Note, improving the logic of the checks is left to subsequent commits, this here only switches from flags to enum. Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 16 Jul, 2013 1 commit
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 06 May, 2013 1 commit
-
-
Janne Grunau authored
Use bitfields in FormatEntry array to avoid wasting an int for each flag.
-
- 19 Jan, 2013 1 commit
-
-
Michael Niedermayer authored
The used flag was mistakenly overlapping with chroma drop Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 29 Nov, 2012 1 commit
-
-
Stefano Sabatini authored
The version number is useful to check the libavutil version against which the library was compiled at run-time, which in turn may be useful to deal with binary compatibility issues.
-
- 31 Oct, 2012 1 commit
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 03 Aug, 2012 1 commit
-
-
Diego Biurrun authored
Refactoring mmx2/mmxext YASM code with cpuflags will force renames. So switching to a consistent naming scheme beforehand is sensible. The name "mmxext" is more official and widespread and also the name of the CPU flag, as reported e.g. by the Linux kernel.
-
- 04 Jul, 2012 2 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
-