diff options
| author | Anton Khirnov <anton@khirnov.net> | 2020-05-22 16:59:46 +0300 |
|---|---|---|
| committer | Anton Khirnov <anton@khirnov.net> | 2020-11-27 17:46:50 +0300 |
| commit | a83098ab03a47179d54a9b9c8bcefc81b9c6aafd (patch) | |
| tree | 3f12682fa2917e3e83b4a3a6459a4be9cf51210d /doc/multithreading.txt | |
| 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/multithreading.txt')
| -rw-r--r-- | doc/multithreading.txt | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/multithreading.txt b/doc/multithreading.txt index 4f645dc147..470194ff85 100644 --- a/doc/multithreading.txt +++ b/doc/multithreading.txt @@ -20,8 +20,7 @@ Slice threading - Frame threading - * Restrictions with slice threading also apply. -* For best performance, the client should set thread_safe_callbacks if it - provides a thread-safe get_buffer() callback. +* Custom get_buffer2() and get_format() callbacks must be thread-safe. * There is one frame of delay added for every thread beyond the first one. Clients must be able to handle this; the pkt_dts and pkt_pts fields in AVFrame will work as usual. |