- 27 Mar, 2017 1 commit
-
-
wm4 authored
The old "API" that signaled rotation as a metadata value has been replaced by DISPLAYMATRIX side data quite a while ago. There is no reason to make muxers/demuxers/API users support both. In addition, the metadata API is dangerous, as user tags could "leak" into it, creating unintended features or bugs. ffmpeg CLI has to be updated to use the new API. In particular, we must not allow to leak the "rotate" tag into the muxer. Some muxers will catch this properly (like mov), but others (like mkv) can add it as generic tag. Note applications, which use libavformat and assume the old rotate API, will interpret such "rotate" user tags as rotate metadata (which it is not), and incorrectly rotate the video. The ffmpeg/ffplay tools drop the use of the old API for muxing and demuxing, as all muxers/demuxers support the new API. This will mean that the tools will not mistakenly interpret per-track "rotate" user tags as rotate metadata. It will _not_ be treated as regression. Unfortunately, hacks have been added, that allow the user to override rotation by setting metadata explicitly, e.g. via -metadata:s:v:0 rotate=0 See references to trac #4560. fate-filter-meta-4560-rotate0 tests this. It's easier to adjust the hack for supporting it than arguing for its removal, so ffmpeg CLI now explicitly catches this case, and essentially replaces the "rotate" value with a display matrix side data. (It would be easier for both user and implementation to create an explicit option for rotation.) When the code under FF_API_OLD_ROTATE_API is disabled, one FATE reference file has to be updated (because "rotate" is not exported anymore). Tested-by:
Michael Niedermayer <michael@niedermayer.cc> Reviewed-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 23 Mar, 2017 2 commits
-
-
wm4 authored
This supports retrieving the device from a provided hw_frames_ctx, and automatically creating a hw_frames_ctx if hw_device_ctx is set. The old API is not deprecated yet. The user can still use av_vdpau_bind_context() (with or without setting hw_frames_ctx), or use the API before that by allocating and setting hwaccel_context manually. Cherry-picked from Libav commit 1a7ddba5. (Adds missing APIchanges entry to the Libav version.) Reviewed-by:
Mark Thompson <sw@jkqxz.net>
-
wm4 authored
This "reuses" the flags introduced for the av_vdpau_bind_context() API function, and makes them available to all hwaccels. This does not affect the current vdpau API, as av_vdpau_bind_context() should obviously override the AVCodecContext.hwaccel_flags flags for the sake of compatibility. Cherry-picked from Libav commit 16a163b5. Reviewed-by:
Mark Thompson <sw@jkqxz.net>
-
- 21 Mar, 2017 1 commit
-
-
wm4 authored
This patch deprecates anything that has to do with merging/splitting side data. Automatic side data merging (and splitting), as well as all API symbols involved in it, are removed completely. Two FF_API_ defines are dedicated to deprecating API symbols related to this: FF_API_MERGE_SD_API removes av_packet_split/merge_side_data in libavcodec, and FF_API_LAVF_KEEPSIDE_FLAG deprecates AVFMT_FLAG_KEEP_SIDE_DATA in libavformat. Since it was claimed that changing the default from merging side data to not doing it is an ABI change, there are two additional FF_API_ defines, which stop using the side data merging/splitting by default (and remove any code in avformat/avcodec doing this): FF_API_MERGE_SD in libavcodec, and FF_API_LAVF_MERGE_SD in libavformat. It is very much intended that FF_API_MERGE_SD and FF_API_LAVF_MERGE_SD are quickly defined to 0 in the next ABI bump, while the API symbols are retained for a longer time for the sake of compatibility. AVFMT_FLAG_KEEP_SIDE_DATA will (very much intentionally) do nothing for most of the time it will still be defined. Keep in mind that no code exists that actually tries to unset this flag for any reason, nor does such code need to exist. Code setting this flag explicitly will work as before. Thus it's ok for AVFMT_FLAG_KEEP_SIDE_DATA to do nothing once side data merging has been removed from libavformat. In order to avoid that anyone in the future does this incorrectly, here is a small guide how to update the internal code on bumps: - next ABI bump (probably soon): - define FF_API_LAVF_MERGE_SD to 0, and remove all code covered by it - define FF_API_MERGE_SD to 0, and remove all code covered by it - next API bump (typically two years in the future or so): - define FF_API_LAVF_KEEPSIDE_FLAG to 0, and remove all code covered by it - define FF_API_MERGE_SD_API to 0, and remove all code covered by it This forces anyone who actually wants packet side data to temporarily use deprecated API to get it all. If you ask me, this is batshit fucked up crazy, but it's how we roll. Making AVFMT_FLAG_KEEP_SIDE_DATA to be set by default was rejected as an ABI change, so I'm going all the way to get rid of this once and for all. Reviewed-by:
James Almer <jamrial@gmail.com> Reviewed-by:
Rostislav Pehlivanov <atomnuker@gmail.com> Reviewed-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 20 Mar, 2017 2 commits
-
-
Clément Bœsch authored
-
Clément Bœsch authored
-
- 18 Mar, 2017 1 commit
-
-
Rostislav Pehlivanov authored
Not used by anything at all since we don't auto insert lavr filters. Reviewed-by:
wm4 <nfxjfg@googlemail.com> Signed-off-by:
Rostislav Pehlivanov <atomnuker@gmail.com>
-
- 07 Mar, 2017 1 commit
-
-
Vittorio Giovara authored
Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 02 Mar, 2017 2 commits
-
-
wm4 authored
If AVVideotoolboxContext.cv_pix_fmt_type is set to 0, don't set the kCVPixelBufferPixelFormatTypeKey value on the VT decoder. This makes VT output its native format, which can be much faster on some hardware iterations (if the native format does not match with the requested format, it will be converted, which is slow). The default is still forcing nv12.
-
wm4 authored
Allow all struct fields to be accessed directly, as long as they're public. Before this change, many fields were "public", but could be accessed via AVOption only. This meant they were effectively not public, but were present for documentation purposes, which was incredibly confusing at best.
-
- 13 Feb, 2017 2 commits
-
-
Mark Thompson authored
For use by codec implementations which can allocate frames internally.
-
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.
-
- 24 Jan, 2017 1 commit
-
-
Marton Balint authored
Return a channel layout and the number of channels based on the specified name. This function is similar to av_get_channel_layout(), but can also parse unknown channel layout specifications. Unknown channel layout specifications are a decimal number and a capital 'C' suffix, in order to not break compatibility with the lowercase 'c' suffix, which is used for a guessed channel layout with the specified number of channels. Signed-off-by:
Marton Balint <cus@passwd.hu>
-
- 22 Jan, 2017 1 commit
-
-
Jonathan Campbell authored
seeds an AVLFG from binary data. Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 17 Jan, 2017 1 commit
-
-
Mark Thompson authored
Deprecates struct vaapi_context and the installed header vaapi.h, to be removed at the next version bump. (cherry picked from commit 851960f6)
-
- 12 Jan, 2017 1 commit
-
-
Nicolas George authored
av_buffersink_get_frame_rate() did already exist; its argument becomes const.
-
- 07 Jan, 2017 1 commit
-
-
softworkz authored
This commit adds the avio_get_dyn_buf function which allows accessing the content of a DynBuffer without destroying it. This is required in matroskaenc for preliminary writing (correct) mkv headers. Context for this change is fixing regression bug #5977. Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 10 Dec, 2016 1 commit
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 07 Dec, 2016 2 commits
-
-
Vittorio Giovara authored
Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
While no decoder currently exports spherical information, this type represents a frame property that has to be passed through from container to frames. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 19 Nov, 2016 1 commit
-
-
James Almer authored
Functionally similar to av_packet_add_side_data(). Allows the use of an already allocated buffer as stream side data. Reviewed-by:
Michael Niedermayer <michael@niedermayer.cc> Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 13 Nov, 2016 2 commits
-
-
Anton Khirnov authored
The Intel binary iHD driver does not support the VASurfaceAttribMemoryType, so surface allocation will fail when using it. (cherry picked from commit 2124711b)
-
Mark Thompson authored
The driver being used is detected inside av_hwdevice_ctx_init() and the quirks field then set from a table of known device. If this behaviour is unwanted, the user can also set the quirks field manually. Also adds the Intel i965 driver quirk (it does not destroy parameter buffers used in a call to vaRenderPicture()) and detects that driver to set it. (cherry picked from commit 4926fa9a)
-
- 09 Nov, 2016 1 commit
-
-
Luca Barbato authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 26 Oct, 2016 2 commits
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 24 Oct, 2016 2 commits
-
-
Rodger Combs authored
Reviewed-By:
Michael Niedermayer <michael@niedermayer.cc>
-
Rodger Combs authored
This allows a consumer to run the muxer's init function without actually writing the header, which is useful in chained muxers that support automatic bitstream filtering.
-
- 22 Oct, 2016 1 commit
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 12 Oct, 2016 3 commits
-
-
Kieran Kunhya authored
Signed-off-by:
Diego Biurrun <diego@biurrun.de>
-
Michael Niedermayer authored
Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This makes them easier to search for.
-
- 02 Oct, 2016 1 commit
-
-
Anton Khirnov authored
The Intel binary iHD driver does not support the VASurfaceAttribMemoryType, so surface allocation will fail when using it.
-
- 30 Sep, 2016 1 commit
-
-
Anton Khirnov authored
-
- 28 Sep, 2016 1 commit
-
-
Anton Khirnov authored
-
- 27 Sep, 2016 3 commits
-
-
Luca Barbato authored
-
James Almer authored
This will allow ffmpeg.c to stop using AVStream.codec in some cases Signed-off-by:
James Almer <jamrial@gmail.com>
-
Michael Niedermayer authored
Found-by:
James Almer <jamrial@gmail.com> Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 23 Sep, 2016 1 commit
-
-
Timo Rothenpieler authored
Reviewed-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 19 Sep, 2016 1 commit
-
-
Yogender Gupta authored
It is supported by the NVIDIA video SDK 7. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-