diff options
| author | wm4 <nfxjfg@googlemail.com> | 2017-05-15 11:27:24 +0200 |
|---|---|---|
| committer | wm4 <nfxjfg@googlemail.com> | 2017-05-15 11:30:36 +0200 |
| commit | 532b23f079b52f4789be1f20ce232286ce4ffa13 (patch) | |
| tree | 2d826fd0046a1c4f2feeb072971292348812b93b /doc | |
| parent | 2c6179aa829e6f50eea6faf47b2b6efd7650a41d (diff) | |
videotoolbox: add hwcontext support
This adds tons of code for no other benefit than making VideoToolbox
support conform with the new hwaccel API (using hw_device_ctx and
hw_frames_ctx).
Since VideoToolbox decoding does not actually require the user to
allocate frames, the new code does mostly nothing.
One benefit is that ffmpeg_videotoolbox.c can be dropped once generic
hwaccel support for ffmpeg.c is merged from Libav.
Does not consider VDA or VideoToolbox encoding.
Fun fact: the frame transfer functions are copied from vaapi, as the
mapping makes copying generic boilerplate. Mapping itself is not
exported by the VT code, because I don't know how to test.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/APIchanges | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/APIchanges b/doc/APIchanges index 09b1a49798..67a6142401 100644 --- a/doc/APIchanges +++ b/doc/APIchanges @@ -15,6 +15,14 @@ libavutil: 2015-08-28 API changes, most recent first: +2017-05-15 - xxxxxxxxxx - lavc 57.96.100 - avcodec.h + VideoToolbox hardware-accelerated decoding now supports the new hwaccel API, + which can create the decoder context and allocate hardware frames automatically. + See AVCodecContext.hw_device_ctx and AVCodecContext.hw_frames_ctx. + +2017-05-15 - xxxxxxxxxx - lavu 57.63.100 - hwcontext.h + Add AV_HWDEVICE_TYPE_VIDEOTOOLBOX and implementation. + 2017-xx-xx - xxxxxxx - lavc 57.95.100 / 57.31.0 - avcodec.h Add AVCodecContext.apply_cropping to control whether cropping is handled by libavcodec or the caller. |