ffserver.texi 9.6 KB
Newer Older
1
\input texinfo @c -*- texinfo -*-
2

3 4 5 6
@settitle FFserver Documentation
@titlepage
@center @titlefont{FFserver Documentation}
@end titlepage
7

8 9 10 11
@top

@contents

12 13 14 15 16 17 18 19 20
@chapter Synopsys

The generic syntax is:

@example
@c man begin SYNOPSIS
ffserver [options]
@c man end
@end example
21

22
@chapter Description
23
@c man begin DESCRIPTION
24

25 26 27 28
FFserver is a streaming server for both audio and video. It supports
several live feeds, streaming from files and time shifting on live feeds
(you can seek to positions in the past on each live feed, provided you
specify a big enough feed storage in ffserver.conf).
29

30 31 32 33 34
FFserver runs in daemon mode by default; that is, it puts itself in
the background and detaches from its TTY, unless it is launched in
debug mode or a NoDaemon option is specified in the configuration
file.

35 36
This documentation covers only the streaming aspects of ffserver /
ffmpeg. All questions about parameters for ffmpeg, codec questions,
37
etc. are not covered here. Read @file{ffmpeg-doc.html} for more
38 39
information.

40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57
@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.

58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
@section Status stream

FFserver supports an HTTP interface which exposes the current status
of the server.

Simply point your browser to the address of the special status stream
specified in the configuration file.

For example if you have:
@example
<Stream status.html>
Format status

# Only allow local people to get the status
ACL allow localhost
ACL allow 192.168.0.0 192.168.255.255
</Stream>
@end example

then the server will post a page with the status information when
the special stream @file{status.html} is requested.

80
@section What can this do?
81 82 83 84 85 86 87 88

When properly configured and running, you can capture video and audio in real
time from a suitable capture card, and stream it out over the Internet to
either Windows Media Player or RealAudio player (with some restrictions).

It can also stream from files, though that is currently broken. Very often, a
web server can be used to serve up the files just as well.

89 90 91
It can stream prerecorded video from .ffm files, though it is somewhat tricky
to make it work correctly.

92
@section What do I need?
93

94
I use Linux on a 900 MHz Duron with a cheapo Bt848 based TV capture card. I'm
Diego Biurrun's avatar
Diego Biurrun committed
95 96
using stock Linux 2.4.17 with the stock drivers. [Actually that isn't true,
I needed some special drivers for my motherboard-based sound card.]
97 98 99

I understand that FreeBSD systems work just fine as well.

100
@section How do I make it work?
101 102

First, build the kit. It *really* helps to have installed LAME first. Then when
103 104
you run the ffserver ./configure, make sure that you have the
@code{--enable-libmp3lame} flag turned on.
105

106
LAME is important as it allows for streaming audio to Windows Media Player.
Diego Biurrun's avatar
Diego Biurrun committed
107
Don't ask why the other audio types do not work.
108

109 110
As a simple test, just run the following two command lines where INPUTFILE
is some file which you can decode with ffmpeg:
111

112
@example
113
./ffserver -f doc/ffserver.conf &
114
./ffmpeg -i INPUTFILE http://localhost:8090/feed1.ffm
115
@end example
116

Diego Biurrun's avatar
Diego Biurrun committed
117
At this point you should be able to go to your Windows machine and fire up
118
Windows Media Player (WMP). Go to Open URL and enter
119

120
@example
121
    http://<linuxbox>:8090/test.asf
122
@end example
123

124
You should (after a short delay) see video and hear audio.
125

126
WARNING: trying to stream test1.mpg doesn't work with WMP as it tries to
Diego Biurrun's avatar
Diego Biurrun committed
127 128
transfer the entire file before starting to play.
The same is true of AVI files.
129

130
@section What happens next?
131

132
You should edit the ffserver.conf file to suit your needs (in terms of
133 134 135
frame rates etc). Then install ffserver and ffmpeg, write a script to start
them up, and off you go.

136
@section Troubleshooting
137

Diego Biurrun's avatar
Diego Biurrun committed
138
@subsection I don't hear any audio, but video is fine.
139

Diego Biurrun's avatar
Diego Biurrun committed
140 141
Maybe you didn't install LAME, or got your ./configure statement wrong. Check
the ffmpeg output to see if a line referring to MP3 is present. If not, then
142
your configuration was incorrect. If it is, then maybe your wiring is not
143
set up correctly. Maybe the sound card is not getting data from the right
144
input source. Maybe you have a really awful audio interface (like I do)
145 146
that only captures in stereo and also requires that one channel be flipped.
If you are one of these people, then export 'AUDIO_FLIP_LEFT=1' before
147 148
starting ffmpeg.

149
@subsection The audio and video loose sync after a while.
150 151 152

Yes, they do.

153
@subsection After a long while, the video update rate goes way down in WMP.
154 155 156

Yes, it does. Who knows why?

157
@subsection WMP 6.4 behaves differently to WMP 7.
158 159 160

Yes, it does. Any thoughts on this would be gratefully received. These
differences extend to embedding WMP into a web page. [There are two
161 162
object IDs that you can use: The old one, which does not play well, and
the new one, which does (both tested on the same system). However,
163 164
I suspect that the new one is not available unless you have installed WMP 7].

165
@section What else can it do?
166

167
You can replay video from .ffm files that was recorded earlier.
168
However, there are a number of caveats, including the fact that the
169
ffserver parameters must match the original parameters used to record the
170
file. If they do not, then ffserver deletes the file before recording into it.
Diego Biurrun's avatar
Diego Biurrun committed
171
(Now that I write this, it seems broken).
172 173 174

You can fiddle with many of the codec choices and encoding parameters, and
there are a bunch more parameters that you cannot control. Post a message
Diego Biurrun's avatar
Diego Biurrun committed
175
to the mailing list if there are some 'must have' parameters. Look in
176 177
ffserver.conf for a list of the currently available controls.

Diego Biurrun's avatar
Diego Biurrun committed
178 179 180
It will automatically generate the ASX or RAM files that are often used
in browsers. These files are actually redirections to the underlying ASF
or RM file. The reason for this is that the browser often fetches the
181 182
entire file before starting up the external viewer. The redirection files
are very small and can be transferred quickly. [The stream itself is
183
often 'infinite' and thus the browser tries to download it and never
184 185
finishes.]

186
@section Tips
187

188
* When you connect to a live stream, most players (WMP, RA, etc) want to
189 190
buffer a certain number of seconds of material so that they can display the
signal continuously. However, ffserver (by default) starts sending data
Diego Biurrun's avatar
Diego Biurrun committed
191
in realtime. This means that there is a pause of a few seconds while the
192
buffering is being done by the player. The good news is that this can be
193
cured by adding a '?buffer=5' to the end of the URL. This means that the
194
stream should start 5 seconds in the past -- and so the first 5 seconds
Diego Biurrun's avatar
Diego Biurrun committed
195
of the stream are sent as fast as the network will allow. It will then
196
slow down to real time. This noticeably improves the startup experience.
197 198 199 200 201 202 203 204 205

You can also add a 'Preroll 15' statement into the ffserver.conf that will
add the 15 second prebuffering on all requests that do not otherwise
specify a time. In addition, ffserver will skip frames until a key_frame
is found. This further reduces the startup delay by not transferring data
that will be discarded.

* You may want to adjust the MaxBandwidth in the ffserver.conf to limit
the amount of bandwidth consumed by live streams.
206

207
@section Why does the ?buffer / Preroll stop working after a time?
208 209 210

It turns out that (on my machine at least) the number of frames successfully
grabbed is marginally less than the number that ought to be grabbed. This
Diego Biurrun's avatar
Diego Biurrun committed
211 212 213
means that the timestamp in the encoded data stream gets behind realtime.
This means that if you say 'Preroll 10', then when the stream gets 10
or more seconds behind, there is no Preroll left.
214

215
Fixing this requires a change in the internals of how timestamps are
216 217
handled.

218
@section Does the @code{?date=} stuff work.
219

Diego Biurrun's avatar
Diego Biurrun committed
220 221
Yes (subject to the limitation outlined above). Also note that whenever you
start ffserver, it deletes the ffm file (if any parameters have changed),
222
thus wiping out what you had recorded before.
223

224
The format of the @code{?date=xxxxxx} is fairly flexible. You should use one
225 226
of the following formats (the 'T' is literal):

227
@example
228 229
* YYYY-MM-DDTHH:MM:SS     (localtime)
* YYYY-MM-DDTHH:MM:SSZ    (UTC)
230
@end example
231

232
You can omit the YYYY-MM-DD, and then it refers to the current day. However
233 234
note that @samp{?date=16:00:00} refers to 16:00 on the current day -- this
may be in the future and so is unlikely to be useful.
235 236

You use this by adding the ?date= to the end of the URL for the stream.
237
For example:   @samp{http://localhost:8080/test.asf?date=2002-07-26T23:05:00}.
238
@c man end
239

240
@chapter Options
241
@c man begin OPTIONS
242

243
@include fftools-common-opts.texi
244

245 246
@section Main options

247
@table @option
248
@item -f @var{configfile}
Diego Biurrun's avatar
Diego Biurrun committed
249
Use @file{configfile} instead of @file{/etc/ffserver.conf}.
250 251 252 253
@item -n
Enable no-launch mode. This option disables all the Launch directives
within the various <Stream> sections. FFserver will not launch any
ffmpeg instance, so you will have to launch them manually.
254 255
@item -d
Enable debug mode. This option increases log verbosity, directs log
256
messages to stdout and causes ffserver to run in the foreground
257
rather than as a daemon.
258 259 260 261 262
@end table
@c man end

@ignore

263
@setfilename ffserver
264 265 266
@settitle FFserver video server

@c man begin SEEALSO
267 268 269

ffmpeg(1), ffplay(1), ffprobe(1), the @file{ffmpeg/doc/ffserver.conf}
example and the FFmpeg HTML documentation
270 271
@c man end

272 273
@c man begin AUTHORS
The FFmpeg developers
274 275 276 277
@c man end

@end ignore

278
@bye