diff options
| author | Anton Khirnov <anton@khirnov.net> | 2020-05-22 15:59:46 +0200 |
|---|---|---|
| committer | Anton Khirnov <anton@khirnov.net> | 2020-11-27 15:46:50 +0100 |
| commit | a83098ab03a47179d54a9b9c8bcefc81b9c6aafd (patch) | |
| tree | 3f12682fa2917e3e83b4a3a6459a4be9cf51210d /doc/APIchanges | |
| parent | 551ca67afe7555368758c4aab476978689380a6d (diff) | |
avcodec: deprecate thread_safe_callbacks
They add considerable complexity to frame-threading implementation,
which includes an unavoidably leaking error path, while the advantages
of this option to the users are highly dubious.
It should be always possible and desirable for the callers to make their
get_buffer2() implementation thread-safe, so deprecate this option.
Diffstat (limited to 'doc/APIchanges')
| -rw-r--r-- | doc/APIchanges | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/APIchanges b/doc/APIchanges index b18f3acaea..bb19cbea7c 100644 --- a/doc/APIchanges +++ b/doc/APIchanges @@ -15,6 +15,11 @@ libavutil: 2017-10-21 API changes, most recent first: +2020-xx-xx - xxxxxxxxxx - lavc 58.114.100 - avcodec.h + Deprecate AVCodecContext.thread_safe_callbacks. Starting with + LIBAVCODEC_VERSION_MAJOR=60, user callbacks must always be + thread-safe when frame threading is used. + 2020-11-25 - xxxxxxxxxx - lavc 58.113.100 - avcodec.h Adds a new flag AV_CODEC_EXPORT_DATA_FILM_GRAIN for export_side_data. |