- 10 Nov, 2017 1 commit
-
-
Michael Niedermayer authored
This gives FFmpeg libs a field that they can freely and safely use. Avoiding the need of wrapping of a users opaque_ref field and its issues. Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 29 Oct, 2017 1 commit
-
-
James Almer authored
The fields can be accessed directly, so these are not needed anymore. Reviewed-by: Paul B Mahol <onemda@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
-
- 23 Oct, 2017 1 commit
-
-
James Almer authored
Signed-off-by: James Almer <jamrial@gmail.com>
-
- 08 Aug, 2017 1 commit
-
-
wm4 authored
Signed-off-by: Anton Khirnov <anton@khirnov.net> Merged from Libav commit 47399ccd.
-
- 26 Jul, 2017 2 commits
-
-
wm4 authored
Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
James Almer authored
Reviwed-by: Rostislav Pehlivanov <atomnuker@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
-
- 06 Apr, 2017 1 commit
-
-
Steve Lhomme authored
As found in HEVC. Signed-off-by: James Almer <jamrial@gmail.com>
-
- 03 Mar, 2017 1 commit
-
-
Michael Niedermayer authored
Found a case where we use size==0, the other related commits remain needed, and should be sufficient to fix the original issue This reverts commit 7e4f32f4. Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 25 Feb, 2017 2 commits
-
-
Michael Niedermayer authored
There should be no case that needs this and its a potential for creating corner cases Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
Michael Niedermayer authored
The size 0 special case causes side data to be created which is different and a special case if for any reasons size = 0 is passed Fixes: multiple runtime error: null pointer passed as argument 1, which is declared to never be null Fixes: 653/clusterfuzz-testcase-5773837415219200 Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/targets/ffmpegSigned-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 13 Feb, 2017 1 commit
-
-
wm4 authored
This is an extended version of the AVFrame.opaque field, which can be used to attach arbitrary user information to an AVFrame. The usefulness of the opaque field is rather limited, because it can store only up to 32 bits of information (or 64 bit on 64 bit systems). It's not possible to set this field to a memory allocation, because there is no way to deallocate it correctly. The opaque_ref field circumvents this by letting the user set an AVBuffer, which makes the user data refcounted. Signed-off-by: Anton Khirnov <anton@khirnov.net> Merges Libav commit 04f3bd34.
-
- 11 Feb, 2017 2 commits
-
-
wm4 authored
This is an extended version of the AVFrame.opaque field, which can be used to attach arbitrary user information to an AVFrame. The usefulness of the opaque field is rather limited, because it can store only up to 32 bits of information (or 64 bit on 64 bit systems). It's not possible to set this field to a memory allocation, because there is no way to deallocate it correctly. The opaque_ref field circumvents this by letting the user set an AVBuffer, which makes the user data refcounted. Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Anton Khirnov authored
This will avoid every caller from hardcoding some specific alignment, which may break in the future with new instruction sets.
-
- 30 Jan, 2017 1 commit
-
-
Marton Balint authored
I wonder how unknown layouts ever worked without this? Reviewed-by: Nicolas George <george@nsup.org> Reviewed-by: Hendrik Leppkes <h.leppkes@gmail.com> Reviewed-by: Paul B Mahol <onemda@gmail.com> Signed-off-by: Marton Balint <cus@passwd.hu>
-
- 12 Jan, 2017 1 commit
-
-
Anton Khirnov authored
Extend the width/height doxy to clarify that it should store coded values.
-
- 16 Nov, 2016 2 commits
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
Michael Niedermayer authored
Fixes null pointer dereference Fixes: 189/FOO Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/targets/ffmpegSigned-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 19 Sep, 2016 1 commit
-
-
Sasi Inguva authored
Signed-off-by: Sasi Inguva <isasi@google.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 25 Jul, 2016 1 commit
-
-
James Almer authored
The accessors are needed only from outside libavutil. Reviewed-by: Michael Niedermayer <michael@niedermayer.cc> Signed-off-by: James Almer <jamrial@gmail.com>
-
- 21 Jun, 2016 1 commit
-
-
Anton Khirnov authored
Currently it's exported as AVFrame.pkt_pts, which is also the only use for that field. The reason it is done like this is that lavc used to export various codec-specific "timing" information in AVFrame.pts, which is not done anymore. Since it is confusing to the callers to have a separate field which is used only for decoder timestamps and nothing else, deprecate pkt_pts and use just AVFrame.pts everywhere.
-
- 05 Jun, 2016 1 commit
-
-
Michael Niedermayer authored
This should detect caes where these functions are called in unclean destinations
-
- 18 Feb, 2016 1 commit
-
-
Diego Biurrun authored
-
- 14 Feb, 2016 1 commit
-
-
Anton Khirnov authored
-
- 13 Feb, 2016 1 commit
-
-
Michael Niedermayer authored
Fixes memleak Fixes: Ticket4899 Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 01 Feb, 2016 1 commit
-
-
Derek Buitenhuis authored
Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
-
- 27 Jan, 2016 1 commit
-
-
Derek Buitenhuis authored
Libav, for some reason, merged this as a public API function. This will aid in future merges. A define is left for backwards compat, just in case some person used it, since it is in a public header. Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
-
- 22 Jan, 2016 1 commit
-
-
Neil Birkbeck authored
Add names for recently added enums to av_frame_side_data_name. Signed-off-by: Neil Birkbeck <neil.birkbeck@gmail.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 11 Jan, 2016 1 commit
-
-
Clément Bœsch authored
Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 08 Dec, 2015 1 commit
-
-
Clément Bœsch authored
-
- 30 Sep, 2015 1 commit
-
-
Vittorio Giovara authored
These field are difficult to interpret, and are provided by a single encoder (mpegvideoenc). In general they do not belong to a structure containing raw data only, so remove them from AVFrame. Mpegvideoenc now uses a private field in Picture for its internal computations. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 05 Sep, 2015 1 commit
-
-
Hendrik Leppkes authored
These fields are still used, removal postponed until a replacement functionality is available.
-
- 22 Aug, 2015 1 commit
-
-
Andreas Cadhalpun authored
Reviewed-by: wm4 <nfxjfg@googlemail.com> Signed-off-by: Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>
-
- 13 Jul, 2015 1 commit
-
-
Michael Niedermayer authored
Fixes: af94b3a3d26586c08f557cafe8246251_signal_sigsegv_7ffff713351a_343_XFMode.ASF with 2097152 alloc limit Found-by: Samuel Groß, Mateusz "j00ru" Jurczyk and Gynvael Coldwind Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 25 Mar, 2015 2 commits
-
-
Ronald S. Bultje authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
Ronald S. Bultje authored
Preparation for following patch. Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 18 Dec, 2014 1 commit
-
-
Luca Barbato authored
And make sure the nb_side_data field is reset as well. Based on an initial patch from wm4 <nfxjfg@googlemail.com>. CC: libav-stable@libav.org
-
- 15 Dec, 2014 1 commit
-
-
wm4 authored
The error path frees all side data, but forgets to reset the side data count. This can blow up later in av_frame_unref() and free_side_data(). Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 29 Aug, 2014 1 commit
-
-
Reimar Döffinger authored
Only "./configure --enable-gpl" on x86 was tested. Signed-off-by: Reimar Döffinger <Reimar.Doeffinger@gmx.de>
-
- 18 Aug, 2014 1 commit
-
-
Clément Bœsch authored
The reasoning behind this addition is that various third party applications are interested in getting some motion information out of a video "for free" when it is available. It was considered to export other information as well (such as the intra information about the block, or the quantization) but the structure might have ended up into a half full-generic, half full of codec specific cruft. If more information is necessary, it should either be added in the "flags" field of the AVMotionVector structure, or in another side-data. This commit also includes an example exporting them in a CSV stream.
-
- 14 Aug, 2014 1 commit
-
-
Diego Biurrun authored
-