- 21 Jun, 2016 1 commit
-
-
Martin Storsjö authored
The functions may not clean up properly after using MMX registers. For the normal testing calls, the checkasm_checked_call functions will do the cleanup (and check that functions that should clean up do it as well), but when benchmarking functions that don't clean up, we don't currently properly clean up at all. This causes issues if a benchmarked function is followed by testing of a function that is supposed to not clobber the MMX/FPU state but doesn't touch it at all. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 20 Jun, 2016 3 commits
-
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
- 17 Jun, 2016 1 commit
-
-
Martin Storsjö authored
The tests are inspired by similar tests for vp9 by Ronald Bultje. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 06 Jun, 2016 1 commit
-
-
Vittorio Giovara authored
Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 26 May, 2016 1 commit
-
-
Anton Khirnov authored
This is a video test and there are no audio packets in the sample anyway.
-
- 25 May, 2016 2 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
-
- 18 May, 2016 2 commits
-
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 17 May, 2016 1 commit
-
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 13 May, 2016 2 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
-
- 04 May, 2016 1 commit
-
-
Vittorio Giovara authored
Signed-off-by:
Diego Biurrun <diego@biurrun.de>
-
- 03 May, 2016 1 commit
-
-
Diego Biurrun authored
-
- 02 May, 2016 1 commit
-
-
Diego Biurrun authored
-
- 27 Apr, 2016 1 commit
-
-
Diego Biurrun authored
-
- 26 Apr, 2016 2 commits
-
-
Vittorio Giovara authored
-
Vittorio Giovara authored
The original sample was generated with invalid software.
-
- 21 Apr, 2016 1 commit
-
-
Diego Biurrun authored
-
- 15 Apr, 2016 2 commits
-
-
Anton Khirnov authored
See commit a7829a2a
-
Anton Khirnov authored
See commit 9d740127
-
- 07 Apr, 2016 1 commit
-
-
Diego Biurrun authored
Restore alphabetical order in lists, break overly long lines, do some prettyprinting, add some explanatory section comments, group parts together that belong together logically.
-
- 06 Apr, 2016 1 commit
-
-
Vittorio Giovara authored
-
- 04 Apr, 2016 2 commits
-
-
Vittorio Giovara authored
-
Vittorio Giovara authored
The current sample comes from an older version of the codec, which supports a single output mode, so rename it accordingly. Add tests for the new pixel formats.
-
- 03 Apr, 2016 1 commit
-
-
Luca Barbato authored
And bump the document version to 4.
-
- 29 Mar, 2016 1 commit
-
-
Vittorio Giovara authored
-
- 24 Mar, 2016 1 commit
-
-
Diego Biurrun authored
-
- 23 Mar, 2016 1 commit
-
-
Diego Biurrun authored
-
- 01 Mar, 2016 2 commits
-
-
Diego Biurrun authored
-
Vittorio Giovara authored
Signed-off-by:
Diego Biurrun <diego@biurrun.de>
-
- 26 Feb, 2016 1 commit
-
-
Diego Biurrun authored
-
- 23 Feb, 2016 4 commits
-
-
Anton Khirnov authored
Currently, AVStream contains an embedded AVCodecContext instance, which is used by demuxers to export stream parameters to the caller and by muxers to receive stream parameters from the caller. It is also used internally as the codec context that is passed to parsers. In addition, it is also widely used by the callers as the decoding (when demuxer) or encoding (when muxing) context, though this has been officially discouraged since Libav 11. There are multiple important problems with this approach: - the fields in AVCodecContext are in general one of * stream parameters * codec options * codec state However, it's not clear which ones are which. It is consequently unclear which fields are a demuxer allowed to set or a muxer allowed to read. This leads to erratic behaviour depending on whether decoding or encoding is being performed or not (and whether it uses the AVStream embedded codec context). - various synchronization issues arising from the fact that the same context is used by several different APIs (muxers/demuxers, parsers, bitstream filters and encoders/decoders) simultaneously, with there being no clear rules for who can modify what and the different processes being typically delayed with respect to each other. - avformat_find_stream_info() making it necessary to support opening and closing a single codec context multiple times, thus complicating the semantics of freeing various allocated objects in the codec context. Those problems are resolved by replacing the AVStream embedded codec context with a newly added AVCodecParameters instance, which stores only the stream parameters exported by the demuxers or read by the muxers.
-
Diego Biurrun authored
Some files may be missing for valid reasons, e.g. on compile failure.
-
Diego Biurrun authored
-
Marton Balint authored
Reviewed-by:
Michael Niedermayer <michaelni@gmx.at> Signed-off-by:
Marton Balint <cus@passwd.hu>
-
- 20 Feb, 2016 1 commit
-
-
Diego Biurrun authored
-
- 18 Feb, 2016 1 commit
-
-
Diego Biurrun authored
-