---
doc/multithreading.txt | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/multithreading.txt b/doc/multithreading.txt
index 70c7fee..9b9ea2d 100644
--- a/doc/multithreading.txt
+++ b/doc/multithreading.txt
@@ -17,12 +17,12 @@ Restrictions on clients
Slice threading -
* If the client uses draw_horiz_band, it must handle it being called from
-separate threads.
+ separate threads.
Frame threading -
* Restrictions with slice threading also apply.
* get_buffer and release_buffer will be called by separate threads, but are
- protected by a mutex.
+ protected by a mutex, so do not need to be reentrant.
* There is one frame of delay added for every thread. Use of reordered_opaque
will help with A/V sync problems, and clients should not assume that no frame
being returned after all frames have been submitted means there are no frames
@@ -38,9 +38,10 @@ Frame threading -
* Relying on previous contents of buffers no longer works. This includes using
reget_buffer() and not copying skipped MBs. Buffers will have age set to
INT_MAX, so this won't be a problem for most cases.
-* Error resilience may not work as well, or deterministically.
* Accepting randomly truncated packets (CODEC_FLAG_TRUNCATED) no longer works.
* Some codecs (such as ffv1) can't be multithreaded.
+* If the codec uses draw_edges, it must be called before
+ ff_report_frame_progress() is called on any row.
Porting codecs to frame threading
==============================================
_______________________________________________
FFmpeg-soc mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-soc
