- 13 Oct, 2015 3 commits
-
-
Derek Buitenhuis authored
Signed-off-by:
Derek Buitenhuis <derek.buitenhuis@gmail.com> Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
There are no formats supporting it anymore and it is deprecated. Update the documentation accordingly.
-
Alexandra Hájková authored
Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
- 12 Oct, 2015 1 commit
-
-
Vittorio Giovara authored
av_dict_set() could return an error, so forward it appropriately. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 11 Oct, 2015 1 commit
-
-
Sean McGovern authored
The versioning facility in the Solaris linker differs from Linux in 3 ways: 1. It does not support globs in linker scripts for symbol versioning -- this is a GNU extension. 2. The linker argument is '-M', instead of '--version-script'. 3. It is picky about line endings. Each symbol or directive must be on a line of it's own. Let's use make_sunver.pl from GCC to generate a version script that works correctly with the Solaris linker. It's function is to correctly expand the globs in the original generated version script. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
- 10 Oct, 2015 3 commits
-
-
Luca Barbato authored
-
Luca Barbato authored
-
Luca Barbato authored
-
- 09 Oct, 2015 1 commit
-
-
Mario Gasparoni authored
Also added dynamic slice_mode option, needed for the max_nal_size. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
- 08 Oct, 2015 2 commits
-
-
Alexandra Hájková authored
Sample-Id: https://samples.libav.org/asf-wmv/demux-asf-assert-failed.wmvSigned-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Anton Khirnov authored
There is not much reason to generate such a small table at runtime. Signed-off-by:
Derek Buitenhuis <derekb@vimeo.com> Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
- 07 Oct, 2015 6 commits
-
-
Hendrik Leppkes authored
This removes the requirement of calling w32thread_init before being able to use the threading primitives. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Hendrik Leppkes authored
The emulation uses native InitOnce* APIs on Windows Vista+, and a lock-free/allocation-free approach using atomics and spinning for Windows XP. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
Prevent a NULL-dereference. CC: libav-stable@libav.org
-
Luca Barbato authored
This way is sufficient to use the component specific configure variable and not guard against the global library configure variable in code that is outside it (e.g. checkasm).
-
Alexandra Khirnova authored
place primary audio coding header data into DCAAudioHeader structure to make DCAContext clearer and move channel related data to DCAChan structure to make them easier to use by extensions Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Vittorio Giovara authored
Do not fail when original resolution is smaller than current one, as the frame buffer is resized automatically. Signed-off-by: Vittorio Giovara <vittorio.giovara at gmail.com>
-
- 04 Oct, 2015 10 commits
-
-
wm4 authored
In some situations, MMAL won't return a decoded frame for certain input frames. This can happen if a frame fails to decode, or if a packet does not actually contain a complete frame. In these situations, we would deadlock (or actually timeout) waiting for an expected output frame, which is not ideal. On the other hand, there are situations where we definitely have to block to avoid deadlocks. (This mess is a consequence of trying to map MMAL's asynchronous and flexible dataflow to libavcodec, which is more static and rigid.) Solve this by doing a blocking wait only if the amount of buffered data is too big. The whole purpose of the blocking wait is to avoid excessive buffering of input data, so we can skip it if it appears to be low. The consequence is that libavcodec can gracefully return no frame to the API user. We want to track the number of full packets to make our heuristic work. But MMAL buffers are fixed-size, requiring splitting large packets. This is why the previous commit is needed. We use the ..._FRAME_END flag to remember packet boundaries, but MMAL does not preserve these buffer flags when returning buffers to the user. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
wm4 authored
The next commit needs 1 bit of additional information per MMAL buffer sent to the MMAL input port. This information will be needed when the buffer is recycled (i.e. returned by the input port's callback). Normally, we could use MMAL_BUFFER_HEADER_FLAG_USER0, but that is unexpectedly not preserved. Do this by storing a pointer to FFBufferEntry in the MMAL buffer's user data, instead of an AVBufferRef. This also changes the lifetime of FFBufferEntry. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Derek Buitenhuis authored
Signed-off-by:
Derek Buitenhuis <derek.buitenhuis@gmail.com> Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Vittorio Giovara authored
Silence an incompatible-pointer-types-discards-qualifiers warning from clang. rangecoder.c:58:34: warning: passing 'uint8_t **' (aka 'unsigned char **') to parameter of type 'const uint8_t **' (aka 'const unsigned char **') discards qualifiers in nested pointer types [-Wincompatible-pointer-types-discards-qualifiers]
-
Vittorio Giovara authored
The intended meaning is "if this block is the first block in a slice then its left boundary is a slice boundary". Silence a logical-not-parentheses warning from gcc.
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
Vittorio Giovara authored
Silence a warning due to frame assignment in dvenc. All uses of the reference in dvdec are read only, except the ones in the main decoding function, so use the frame pointer directly there.
-
Vittorio Giovara authored
Silence an uninitialized warning from clang.
-
- 03 Oct, 2015 5 commits
-
-
Anton Khirnov authored
The public API should not depend on the build configuration.
-
Anton Khirnov authored
-
Henrik Gramner authored
They're short enough that inlining them actually reduces code size due to all the overhead associated with making a function call. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
John Stebbins authored
"language" is not an offical matroska tag. Track languages are specified with the MATROSKA_ID_TRACKLANGUAGE ebml. Writing the tag overrides the ebml specified language during playback with libav and some other players. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
Henrik Gramner authored
The previous implementation was behaving incorrectly in some corner cases. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
- 02 Oct, 2015 4 commits
-
-
Christophe Gisquet authored
CID 1256 is specified as using the same table for luma and chroma, which is the same as CID 1235 luma table. This is consistent with the format supposedly being RGB, although most sequences seem to actually be YCbCr-encoded. Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc> Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Jeremy James authored
Tables 1258 and 1259 were not zigzagged when added, so it was not possible to notice the equivalence. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Jeremy James authored
These table was not zigzagged when added. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Joseph Artsimovich authored
Convert them to zigzag order, as the rest of them are. When I was adding support for 10-bit DNxHD, I just copy-pasted the missing quant matrices from the spec. Now it turns out the existing matrices in dnxhddata.c were in zigzag order. This resulted in wrong quantization for 10-bit DNxHD. The attached patch fixes the problem by converting 10-bit quant matrices to zigzag order. Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 01 Oct, 2015 4 commits
-
-
Derek Buitenhuis authored
When forwarding the frame type information, by default x264 can decide which kind of keyframe output, add an option to force it to output IDR frames in to support use-cases such as preparing the content for segmented streams formats.
-
Yu Xiaolei authored
x264 build 147 adds the native support for NV21. Useful to avoid additional pixel format conversion when encoding from a wide range of capture devices, Android among those. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
Bug-Id: CID 1320426
-
Alexandra Khirnova authored
Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-