- 17 Jan, 2019 1 commit
-
-
Guo, Yejun authored
The encoders such as libx264 support different QPs offset for different MBs, it makes possible for ROI-based encoding. It makes sense to add support within ffmpeg to generate/accept ROI infos and pass into encoders. Typical usage: After AVFrame is decoded, a ffmpeg filter or user's code generates ROI info for that frame, and the encoder finally does the ROI-based encoding. The ROI info is maintained as side data of AVFrame. Signed-off-by:
Guo, Yejun <yejun.guo@intel.com> Signed-off-by:
Derek Buitenhuis <derek.buitenhuis@gmail.com>
-
- 21 Dec, 2018 1 commit
-
-
Mohammad Izadi authored
The dynamic metadata contains data for color volume transform - application 4 of SMPTE 2094-40:2016 standard. The data comes from HEVC in the SEI_TYPE_USER_DATA_REGISTERED_ITU_T_T35. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 24 Nov, 2018 1 commit
-
-
Martin Vignali authored
-
- 06 Nov, 2018 1 commit
-
-
Carl Eugen Hoyos authored
Based on 7471352f by Luca Barbato. Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 05 Nov, 2018 2 commits
-
-
Martin Storsjö authored
This was marked as deprecated (but only in the doxygen, not with an actual deprecation attribute) in 81c623fa in 2011, but was undeprecated in ad1ee5fa. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This was marked as deprecated (but only in the doxygen, not with an actual deprecation attribute) in 81c623fa in 2011, but was undeprecated in ad1ee5fa. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 01 Nov, 2018 2 commits
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 27 Oct, 2018 1 commit
-
-
Michael Niedermayer authored
This is needed because of 32bit float formats (which are difficult to store in 16bits) This also fixes undefined behavior found by fate Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 24 Oct, 2018 1 commit
-
-
Josh de Kock authored
-
- 09 Sep, 2018 1 commit
-
-
Marton Balint authored
Signed-off-by:
Marton Balint <cus@passwd.hu>
-
- 11 Aug, 2018 1 commit
-
-
Sergey Lavrushkin authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 09 May, 2018 2 commits
-
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
- 30 Apr, 2018 1 commit
-
-
Marton Balint authored
Signed-off-by:
Marton Balint <cus@passwd.hu>
-
- 26 Apr, 2018 2 commits
-
-
Clément Bœsch authored
-
Clément Bœsch authored
-
- 16 Apr, 2018 2 commits
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 03 Apr, 2018 1 commit
-
-
wm4 authored
PSEUDOPAL pixel formats are not paletted, but carried a palette with the intention of allowing code to treat unpaletted formats as paletted. The palette simply mapped the byte values to the resulting RGB values, making it some sort of LUT for RGB conversion. It was used for 1 byte formats only: RGB4_BYTE, BGR4_BYTE, RGB8, BGR8, GRAY8. The first 4 are awfully obscure, used only by some ancient bitmap formats. The last one, GRAY8, is more common, but its treatment is grossly incorrect. It considers full range GRAY8 only, so GRAY8 coming from typical Y video planes was not mapped to the correct RGB values. This cannot be fixed, because AVFrame.color_range can be freely changed at runtime, and there is nothing to ensure the pseudo palette is updated. Also, nothing actually used the PSEUDOPAL palette data, except xwdenc (trivially changed in the previous commit). All other code had to treat it as a special case, just to ignore or to propagate palette data. In conclusion, this was just a very strange old mechnaism that has no real justification to exist anymore (although it may have been nice and useful in the past). Now it's an artifact that makes the API harder to use: API users who allocate their own pixel data have to be aware that they need to allocate the palette, or FFmpeg will crash on them in _some_ situations. On top of this, there was no API to allocate the pseuo palette outside of av_frame_get_buffer(). This patch not only deprecates AV_PIX_FMT_FLAG_PSEUDOPAL, but also makes the pseudo palette optional. Nothing accesses it anymore, though if it's set, it's propagated. It's still allocated and initialized for compatibility with API users that rely on this feature. But new API users do not need to allocate it. This was an explicit goal of this patch. Most changes replace AV_PIX_FMT_FLAG_PSEUDOPAL with FF_PSEUDOPAL. I first tried #ifdefing all code, but it was a mess. The FF_PSEUDOPAL macro reduces the mess, and still allows defining FF_API_PSEUDOPAL to 0. Passes FATE with FF_API_PSEUDOPAL enabled and disabled. In addition, FATE passes with FF_API_PSEUDOPAL set to 1, but with allocation functions manually changed to not allocating a palette.
-
- 24 Mar, 2018 1 commit
-
-
Jacob Trimble authored
This new side-data will contain info on how a packet is encrypted. This allows the app to handle packet decryption. Signed-off-by:
Jacob Trimble <modmaker@google.com> Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 18 Mar, 2018 1 commit
-
-
wm4 authored
This adds a way for an API user to transfer QP data and metadata without having to keep the reference to AVFrame, and without having to explicitly care about QP APIs. It might also provide a way to finally remove the deprecated QP related fields. In the end, the QP table should be handled in a very similar way to e.g. AV_FRAME_DATA_MOTION_VECTORS. There are two side data types, because I didn't care about having to repack the QP data so the table and the metadata are in a single AVBufferRef. Otherwise it would have either required a copy on decoding (extra slowdown for something as obscure as the QP data), or would have required making intrusive changes to the codecs which support export of this data. The new side data types are added under deprecation guards, because I don't intend to change the status of the QP export as being deprecated (as it was before this patch too).
-
- 16 Mar, 2018 1 commit
-
-
James Almer authored
Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 10 Mar, 2018 1 commit
-
-
James Almer authored
Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 01 Mar, 2018 1 commit
-
-
Rostislav Pehlivanov authored
Signed-off-by:
Rostislav Pehlivanov <atomnuker@gmail.com>
-
- 13 Feb, 2018 1 commit
-
-
wm4 authored
These were needed for ABI compatibility with Libav. We don't need them anymore.
-
- 24 Dec, 2017 1 commit
-
-
James Darnley authored
-
- 15 Dec, 2017 1 commit
-
-
Aman Gupta authored
Signed-off-by:
Matthieu Bouron <matthieu.bouron@gmail.com>
-
- 04 Dec, 2017 1 commit
-
-
Andrew D'Addesio authored
Add av_sat_sub32 and av_sat_dsub32 as the subtraction analogues to av_sat_add32/av_sat_dadd32. Also clarify the formulas for dadd32/dsub32. Signed-off-by:
Andrew D'Addesio <modchipv12@gmail.com>
-
- 28 Nov, 2017 1 commit
-
-
Vittorio Giovara authored
Implement detection in h264 and hevc and insertion in framepack filter. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 25 Nov, 2017 1 commit
-
-
Mark Thompson authored
This was added for compatibility with libav, by leaving a space for formats added in libav to be merged. Since that feature has been removed, we don't need a gap here. Reviewed-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 22 Nov, 2017 2 commits
-
-
Mark Thompson authored
-
Mark Thompson authored
-
- 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>
-
- 22 Oct, 2017 1 commit
-
-
James Almer authored
Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 11 Oct, 2017 1 commit
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 10 Oct, 2017 1 commit
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 21 Sep, 2017 2 commits
-
-
Vittorio Giovara authored
Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 13 Sep, 2017 1 commit
-
-
Mark Thompson authored
-