- 28 Mar, 2016 10 commits
-
-
Anton Khirnov authored
Stop using the H264Context ones, to allow removing the H264Context dependency.
-
Anton Khirnov authored
There is no need for them to be extern anymore.
-
Anton Khirnov authored
-
Anton Khirnov authored
The ~100 lines of shared code is not worth the pain of svq3 messing with h264 internals.
-
Anton Khirnov authored
This will allow decoupling the parser from the decoder.
-
Anton Khirnov authored
This is required by h264.
-
Anton Khirnov authored
-
Anton Khirnov authored
This should make it more clear that it is not supposed to be used for anything except logging.
-
Anton Khirnov authored
-
Anton Khirnov authored
This code will be shared with h264.
-
- 26 Mar, 2016 1 commit
-
-
Martin Storsjö authored
Previously, ff_h264_idct_add_neon (originally in the arm version) used a non-regular transpose in order to be able to use more instructions that deal with registers as 128 bit register pairs. The aarch64 translation doesn't do it to the same extent, but brought along the same structure since it was a straight translation. This reshuffles ff_h264_idct_add_neon, bringing it closer to the C implementation, making the transpose_4x4H macro do a regular transpose, usable for other algorithms as well. Previously, the third and fourth output from transpose_4x4H were swapped, and prior to cc29d96d, the same inputs as well. In addition to just swapping the outputs, also renumber the intermediate registers for better readability (making the register order match transpose_4x8B). This runs with the same number of cycles as before. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 25 Mar, 2016 16 commits
-
-
Ico Doornekamp authored
The problem is that the argument 'q' is of the type uint8_t. According to the JPEG standard, if 1 <= q <= 50, the scale factor 'S' should be 5000 / Q. Because the create_default_qtables() reuses the variable 'q' to store the result of this calculation, for small values of q < 19, q wil subsequently overflow and give wrong results in the calculated quantization tables. Instead, use a new variable 'S' (same name as in RFC2435) with the proper range to store the result of the division. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Vittorio Giovara authored
Helps in decoupling this code from mpegvideo.
-
Vittorio Giovara authored
It will be needed to initialize BlockDSP in the next commit.
-
Vittorio Giovara authored
Helps in decoupling this code from mpegvideo.
-
Vittorio Giovara authored
The size of the block is fixed (8x8 plus padding).
-
Vittorio Giovara authored
Helps in decoupling this code from mpegvideo.
-
Vittorio Giovara authored
Helps in decoupling this code from mpegvideo.
-
Vittorio Giovara authored
Use it instead of the embedded mpegvideo one. Update init function signature to load it directly from the callers.
-
Vittorio Giovara authored
-
Vittorio Giovara authored
These buffers are just a way to store frame pointers and be able to modify them without touching the original ones. The two dependent decoders (WMV2 and VC1) do not need special care for these fields: the former does not seem to use the dest buffers, while the latter reinits them every time to the current frame data buffers. So only keep a local copy rather than the one from mpegvideo.
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Anton Khirnov authored
The test uses printf.
-
Anton Khirnov authored
-
Anton Khirnov authored
CC: libav-stable@libav.org
-
- 24 Mar, 2016 12 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
This is already taken care of by CLEANSUFFIXES.
-
Diego Biurrun authored
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Apply the default value for timeout in code instead of via the avoption, to allow distinguishing the default value from the user not setting anything at all. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Since all URLContexts have the same AVOptions, such AVOptions will be applied on the outermost context only and removed from the dict, while they probably make sense on all contexts. This makes sure that rw_timeout gets propagated to the innermost URLContext (to make sure it gets passed to the tcp protocol, when opening a http connection for instance). Alternatively, such matching options would be kept in the dict and only removed after the ffurl_connect call. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Michael Niedermayer authored
This includes documentation and other modifications by Lukasz Marek and Martin Storsjö. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Lukasz Marek authored
Also add const to pointers in static functions within opt.c where possible/necessary. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Using this requires setting the rw_timeout option to make it terminate, alternatively using the interrupt callback (if used via the API). Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Andrey Utkin authored
If set non-zero, this limits duration of the retry_transfer_wrapper() loop, thus affecting ffurl_read*(), ffurl_write(). As soon as one single byte is successfully received/transmitted, the timer restarts. This has further changes by Michael Niedermayer and Martin Storsjö. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Currently the list of avoptions for URLContext is empty though, but such options will be added. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 23 Mar, 2016 1 commit
-
-
Anton Khirnov authored
-