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.
Showing the changes to doc/APIchanges (1 of 8 files). Show all
Unified · Split
| @@ -15,6 +15,11 @@ libavutil: 2017-10-21 · 14 unmodified lines | |||
| 15 | 15 | ||
| 16 | API changes, most recent first: | 16 | API changes, most recent first: |
| 17 | 17 | ||
| 18 | 2020-xx-xx - xxxxxxxxxx - lavc 58.114.100 - avcodec.h | ||
| 19 | Deprecate AVCodecContext.thread_safe_callbacks. Starting with | ||
| 20 | LIBAVCODEC_VERSION_MAJOR=60, user callbacks must always be | ||
| 21 | thread-safe when frame threading is used. | ||
| 22 | |||
| 18 | 2020-11-25 - xxxxxxxxxx - lavc 58.113.100 - avcodec.h | 23 | 2020-11-25 - xxxxxxxxxx - lavc 58.113.100 - avcodec.h |
| 19 | Adds a new flag AV_CODEC_EXPORT_DATA_FILM_GRAIN for export_side_data. | 24 | Adds a new flag AV_CODEC_EXPORT_DATA_FILM_GRAIN for export_side_data. |
| 20 | 25 | ||