[FFmpeg-devel] [PATCH] doc/protocols: explain FTP truncuation problem

Lukasz Marek lukasz.m.luki2 at gmail.com
Fri Apr 3 00:45:34 CEST 2015


Signed-off-by: Lukasz Marek <lukasz.m.luki2 at gmail.com>
---
 doc/protocols.texi | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/doc/protocols.texi b/doc/protocols.texi
index 2a19b41..73c511c 100644
--- a/doc/protocols.texi
+++ b/doc/protocols.texi
@@ -183,7 +183,11 @@ to be seekable. Default value is 0.
 NOTE: Protocol can be used as output, but it is recommended to not do
 it, unless special care is taken (tests, customized server configuration
 etc.). Different FTP servers behave in different way during seek
-operation. ff* tools may produce incomplete content due to server limitations.
+operation. Some servers will overwrite existing data after seeking backward,
+which is expected by FFmpeg, but some servers truncate file at new position.
+Unless FFmpeg can seek backward without truncuation, it may produce incomplete
+or corrupted content. Some FTP servers behave in expected way by default,
+some are configurable, some cannot be used to store files directly.
 
 @section gopher
 
-- 
1.9.1



More information about the ffmpeg-devel mailing list