diff options
author | Stefano Sabatini <stefano.sabatini-lala@poste.it> | 2008-06-19 01:48:56 +0400 |
---|---|---|
committer | Stefano Sabatini <stefano.sabatini-lala@poste.it> | 2008-06-19 01:48:56 +0400 |
commit | f26a60a0f0d04436d8c39e13930bb2a74dc0d3c2 (patch) | |
tree | 34191e7a4a1eabe2a9d9ab20ca386159f67104c2 /doc | |
parent | 4714776b6af0ff11bbd9130b4c2239c56ea940a9 (diff) |
Add an "How does it work" section in ffserver-doc.texi.
Originally committed as revision 13808 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'doc')
-rw-r--r-- | doc/ffserver-doc.texi | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/ffserver-doc.texi b/doc/ffserver-doc.texi index e93d70f021..4df422dcfe 100644 --- a/doc/ffserver-doc.texi +++ b/doc/ffserver-doc.texi @@ -26,6 +26,24 @@ information. [Contributed by Philip Gladstone, philip-ffserver at gladstonefamily dot net] +@section How does it work? + +FFserver receives prerecorded files or FFM streams from some ffmpeg +instance as input, then streams them over RTP/RTSP/HTTP. + +An ffserver instance will listen on some port as specified in the +configuration file. You can launch one or more instances of ffmpeg and +send one or more FFM streams to the port where ffserver is expecting +to receive them. Alternately, you can make ffserver launch such ffmpeg +instances at startup. + +Input streams are called feeds, and each one is specified by a <Feed> +section in the configuration file. + +For each feed you can have different output streams in various +formats, each one specified by a <Stream> section in the configuration +file. + @section What can this do? When properly configured and running, you can capture video and audio in real |