[FFmpeg-cvslog] r24616 - in trunk: Makefile doc/ffmpeg-doc.texi doc/ffplay-doc.texi doc/ffprobe-doc.texi doc/protocols.texi
stefano
subversion
Sat Jul 31 17:45:29 CEST 2010
Author: stefano
Date: Sat Jul 31 17:45:29 2010
New Revision: 24616
Log:
Add protocols.texi.
Added:
trunk/doc/protocols.texi
Modified:
trunk/Makefile
trunk/doc/ffmpeg-doc.texi
trunk/doc/ffplay-doc.texi
trunk/doc/ffprobe-doc.texi
Modified: trunk/Makefile
==============================================================================
--- trunk/Makefile Sat Jul 31 16:50:51 2010 (r24615)
+++ trunk/Makefile Sat Jul 31 17:45:29 2010 (r24616)
@@ -115,9 +115,9 @@ documentation: $(addprefix doc/, develop
$(HTMLPAGES) $(MANPAGES): doc/fftools-common-opts.texi
-doc/ffmpeg.pod doc/ffmpeg-doc.html: doc/indevs.texi doc/filters.texi doc/outdevs.texi
-doc/ffplay.pod doc/ffplay-doc.html: doc/indevs.texi doc/filters.texi doc/outdevs.texi
-doc/ffprobe.pod doc/ffprobe-doc.html: doc/indevs.texi
+doc/ffmpeg.pod doc/ffmpeg-doc.html: doc/indevs.texi doc/filters.texi doc/outdevs.texi doc/protocols.texi
+doc/ffplay.pod doc/ffplay-doc.html: doc/indevs.texi doc/filters.texi doc/outdevs.texi doc/protocols.texi
+doc/ffprobe.pod doc/ffprobe-doc.html: doc/indevs.texi doc/protocols.texi
doc/%.html: TAG = HTML
doc/%.html: doc/%.texi
Modified: trunk/doc/ffmpeg-doc.texi
==============================================================================
--- trunk/doc/ffmpeg-doc.texi Sat Jul 31 16:50:51 2010 (r24615)
+++ trunk/doc/ffmpeg-doc.texi Sat Jul 31 17:45:29 2010 (r24616)
@@ -745,19 +745,6 @@ The following constants are available:
@c man end
- at section Protocols
-
-The file name can be @file{-} to read from standard input or to write
-to standard output.
-
-FFmpeg also handles many protocols specified with an URL syntax.
-
-Use 'ffmpeg -protocols' to see a list of the supported protocols.
-
-The protocol @code{http:} is currently used only to communicate with
-FFserver (see the FFserver documentation). When FFmpeg will be a
-video player it will also be used for streaming :-)
-
@chapter Tips
@c man begin TIPS
@@ -966,6 +953,7 @@ file to which you want to add them.
@include indevs.texi
@include outdevs.texi
+ at include protocols.texi
@include filters.texi
@ignore
Modified: trunk/doc/ffplay-doc.texi
==============================================================================
--- trunk/doc/ffplay-doc.texi Sat Jul 31 16:50:51 2010 (r24615)
+++ trunk/doc/ffplay-doc.texi Sat Jul 31 17:45:29 2010 (r24616)
@@ -155,6 +155,7 @@ Seek to percentage in file corresponding
@include indevs.texi
@include outdevs.texi
+ at include protocols.texi
@include filters.texi
@ignore
Modified: trunk/doc/ffprobe-doc.texi
==============================================================================
--- trunk/doc/ffprobe-doc.texi Sat Jul 31 16:50:51 2010 (r24615)
+++ trunk/doc/ffprobe-doc.texi Sat Jul 31 17:45:29 2010 (r24616)
@@ -112,6 +112,7 @@ with name ``STREAM''.
@end table
@c man end
+ at include protocols.texi
@include indevs.texi
@ignore
Added: trunk/doc/protocols.texi
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ trunk/doc/protocols.texi Sat Jul 31 17:45:29 2010 (r24616)
@@ -0,0 +1,220 @@
+ at chapter Protocols
+ at c man begin PROTOCOLS
+
+Protocols are configured elements in FFmpeg which allow to access
+resources which require the use of a particular protocol.
+
+When you configure your FFmpeg build, all the supported protocols
+are enabled by default. You can list them using the configure option
+"--list-protocols".
+
+You can disable all the protocols using the configure option
+"--disable-protocols", and selectively enable a protocol using the
+option "--enable-protocol=@var{PROTOCOL}", or you can disable a
+particular protocol using the option
+"--disable-protocol=@var{PROTOCOL}".
+
+The option "-protocols" of the ff* tools will display the list of
+the supported protocols.
+
+A description of the currently available protocols follows.
+
+ at section concat
+
+Physical concatenation protocol.
+
+Allow to read and seek from many resource in sequence as they were an
+unique resource.
+
+An url accepted by this protocol has the syntax:
+ at example
+concat:@var{URL1}|@var{URL2}|...|@var{URLN}
+ at end example
+
+where @var{URL1}, @var{URL2}, ..., @var{URLN} are the urls of the
+resource to be concatenated, each one possibly specifying a distinct
+protocol.
+
+For example to read a sequence of files @file{split1.mpeg},
+ at file{split2.mpeg}, @file{split3.mpeg} with @file{ffplay} use the
+command:
+ at example
+ffplay concat:split1.mpeg\|split2.mpeg\|split3.mpeg
+ at end example
+
+Note that you may need to escape the character "|" which is special for
+many shells.
+
+ at section file
+
+File access protocol.
+
+Allow to read from or read to a file.
+
+For example to read from a file @file{input.mpeg} with @file{ffmpeg}
+use the command:
+ at example
+ffmpeg -i file:input.mpeg output.mpeg
+ at end example
+
+Note that if not specified otherwise, the ff* tools will use the file
+protocol by default, that is a resource specified with the name
+"FILE.mpeg" is interpreted as it were the url "file:FILE.mpeg".
+
+ at section gopher
+
+Gopher protocol.
+
+ at section http
+
+HTTP (Hyper Text Trasfer Protocol).
+
+ at section mmst
+
+MMS (Microsoft Media Server) protocol over TCP.
+
+ at section md5
+
+MD5 output protocol.
+
+Computes the MD5 hash of data written, and on close writes this to the
+designated output or stdout if none is specified. It can be used to
+test muxers without writing an actual file.
+
+Some examples follow.
+ at example
+# write the MD5 hash of the encoded AVI file in the file output.avi.md5
+ffmpeg -i input.flv -f avi -y md5:output.avi.md5
+
+# write the MD5 hash of the encoded AVI file to stdout
+ffmpeg -i input.flv -f avi -y md5:
+ at end example
+
+Note that some formats (typically mov) require the output protocol to
+be seekable, so they will fail with the MD5 output protocol.
+
+ at section pipe
+
+UNIX pipe access protocol.
+
+Allow to read and write from UNIX pipes.
+
+The accepted syntax is:
+ at example
+pipe:[@var{number}]
+ at end example
+
+ at var{number} is the number corresponding to the file descriptor of the
+pipe (e.g. 0 for stdin, 1 for stdout, 2 for stderr).
+If @var{number} is not specified will use by default stdout if the
+protocol is used for writing, stdin if the protocol is used for
+reading.
+
+For example to read from stdin with @file{ffmpeg}:
+ at example
+cat test.wav | ffmpeg -i pipe:0
+# this is the same as
+cat test.wav | ffmpeg -i pipe:
+ at end example
+
+For writing to stdout with @file{ffmpeg}:
+ at example
+ffmpeg -i test.wav -f avi pipe:1 | cat > test.avi
+# this is the same as
+ffmpeg -i test.wav -f avi pipe: | cat > test.avi
+ at end example
+
+Note that some formats (typically mov), require the output protocol to
+be seekable, so they will fail with the pipe output protocol.
+
+ at section rtmp
+
+Real-Time Messaging Protocol.
+
+The Real-Time Messaging Protocol (RTMP) is used for streaming multime?
+dia content across a TCP/IP network.
+
+The required syntax is:
+ at example
+rtmp://@var{server}[:@var{port}][/@var{app}][/@var{playpath}]
+ at end example
+
+Follows the description of the accepted parameters.
+ at table @option
+
+ at item server
+It is the address of the RTMP server.
+
+ at item port
+It is the number of the TCP port to use (by default is 1935).
+
+ at item app
+It is the name of the application to acces. It usually corresponds to
+the the path where the application is installed on the RTMP server
+(e.g. @file{/ondemand/}, @file{/flash/live/}, etc.).
+
+ at item playpath
+It is the path or name of the resource to play with reference to the
+application specified in @var{app}, may be prefixed by "mp4:".
+
+ at end table
+
+For example to read with @file{ffplay} a multimedia resource named
+"sample" from the application "vod" from an RTMP server "myserver":
+ at example
+ffplay rtmp://myserver/vod/sample
+ at end example
+
+ at section rtmp, rtmpe, rtmps, rtmpt, rtmpte
+
+Real-Time Messaging Protocol and its variants supported through
+librtmp.
+
+Require the presence of the headers and library of librtmp during
+configuration. You need to explicitely configure the build with
+"--enable-librtmp". If enabled this will replace the native RTMP
+protocol.
+
+This protocol provides most client functions and a few server
+functions needed to support RTMP, RTMP tunneled in HTTP (RTMPT),
+encrypted RTMP (RTMPE), RTMP over SSL/TLS (RTMPS) and tunneled
+variants of these encrypted types (RTMPTE, RTMPTS).
+
+The required syntax is:
+ at example
+ at var{rtmp_proto}://@var{server}[:@var{port}][/@var{app}][/@var{playpath}] @var{options}
+ at end example
+
+where @var{rtmp_proto} is one of the strings "rtmp", "rtmpt", "rtmpe",
+"rtmps", "rtmpte", "rtmpts" corresponding to each RTMP variant, and
+ at var{server}, @var{port}, @var{app} and @var{playpath} have the same
+meaning has specified for the RTMP native protocol.
+ at var{options} contains a list of space-separated options of the form
+ at var{key}=@var{val}.
+
+See the manual page of librtmp (man 3 librtmp) for more information.
+
+For example, to stream a file in real-time to an RTMP server using
+ at file{ffmpeg}:
+ at example
+ffmpeg -re -i myfile -f flv rtmp://myserver/live/mystream
+ at end example
+
+To play the same stream using @file{ffplay}:
+ at example
+ffplay "rtmp://myserver/live/mystream live=1"
+ at end example
+
+ at section rtp
+
+Real-Time Protocol.
+
+ at section tcp
+
+Trasmission Control Protocol.
+
+ at section udp
+
+User Datagram Protocol.
+
+ at c man end PROTOCOLS
More information about the ffmpeg-cvslog
mailing list