[FFmpeg-devel] [DOC] FFSERVER Configuration Files.

[Piero Bugoni]

This note addresses the changes suggested below:

> 
> > --- ffserver.conf-swf	(revision 0)
> > +++ ffserver.conf-swf	(revision 0)
> > @@ -0,0 +1,46 @@
> > +<Stream test1.swf>
> > +Feed feed1.ffm
> > +Format swf
> > +AudioBitRate 64k         # try 64, 128, or 256
> > +AudioCodec mp3           # swf uses mp3 codec
> 
> MP3 audio, same below

Done.

> 
> > --- ffserver.conf-mp3	(revision 0)
> > +++ ffserver.conf-mp3	(revision 0)
> > @@ -0,0 +1,60 @@
> > +# A tested-working ffserver.conf setup
> > +# for an audio-only mp3 stream across
> > +# 100Mbit capable testbench-LAN.
> > +
> > +# Machine was a 1100 Celeron  with 512M RAM.
> > +# ffserver and ffmpeg run on same machine with
> > +# Apache webserver.
> 
> the/an Apache, same below
> 

Done.



> Why are you keeping lines so short here?  same below ..
> 

Not much to be said here, so line is short. 
> > +MaxClients 10               # Probably safe, max = 1000
> > +MaxBandwidth 16000          # 16 Mbit/s.


 

> 
> nits: unnecessary capitalization and period, same below

Tried to get "Brand Names" correct.
> 
> > +# Works with MPlayer, and MS MediaPlayer,and MPlayer Firefox Plugin
> 
> Leave out the commas if you use "and" and don't forget the spaces after
> a comma.

Fixed. Comma after "MediaPlayer" is to separate back reference from "Plugin" so
as not to infer there is a MPlayer plugin for MS Media Player.

> 
> > +# Stream may take 10 to 20 seconds to start in MPlayer Plugin
> 
> plugin

Fixed. (I think).

> 
> > --- ffserver.conf-3cam-adsl-flv	(revision 0)
> > +++ ffserver.conf-3cam-adsl-flv	(revision 0)
> > @@ -0,0 +1,153 @@
> > +# A tested-working ffserver.conf setup
> > +# for  repeating  3 streams coming from an ffmpeg machine
> 
> two spaces?
> 

All such cleaned up.

> > +# over an adsl connection to dedicated server.
> 
> ADSL, to a dedicated
Done.

> 
> > +# bandwidth to server was around 320 Kb/s.
> 
> Capitalize.
Done.


> 
> > +# ffserver was run on a dedicated
> > +# leased server, 2.8 P4, 512 RAM,
> 
> 2.8GHz, 512MB
Done. 

> 
> > +# ffmpeg was run on local server, and sent streams to
> > +# ffserver machine over DSL
> 
> on the/a local, to the/a ffserver
Fixed.



> 
> > +# This file should work as-is, except that the
> > +# IP Address of the machine sending the streams
> 
> address

Done. (Personally I think "IP Address" is the complete proper noun. After all,
The address in question is not just any address, but the "IP" address).

> 
> > +# to ffserver needs to be entered in the Feed Definitions.
> 
> feed definitions
Fixed but I think significant elements in the conf files should be emphasized.


> 
> > +# (See Below).
> 
> see below
done.

> 
> > +# ffserver and ffmpeg 2 separate machines.
> 
> on 2 separate
Done.

> 
> > +# With Firefox a stream can be tested directly by pointing the
> > +# browser to it like: http://<ffserver-host>:8090/test1.flv
> 
> s/it like//, same below
I wrote this way to indicate that a person points a browser to a stream.
Because many streams can be set up, and even multiple ports (and ffserver
instances, I think,) I wanted people to think in terms of pointing a browser to
a stream, as opposed to a machine, IP address.


> 
> > +#  For NTSC Try Frame Rates of 1, 3, or 9.99.
> 
> try framerates
Done.


> 
> > +# The Q	value is pretty important here. Values of around 5 to 7.5
> 
> Why the spaces?  same below

Wasn't written that way. Must've got mangled.

> 
> > +# in this instance values grater than 10 will probably make image
> indiscernable.
> 
> grEater, s/indiscernable/unrecognizable/
Done.

> 
> > +# Flash Player has a limit of 16,500 frames.
> > +# When using a browser, it is necessary to refresh the viewing
> > +# page periodically, or the stream will block.
> 
> refresh the viewed page / refresh the page being viewed, same below

Fixed.

> 
> > +# IntraOnly: This is like specifying VideoGOPSize 0, or -g 0 on the
> > +# command line for ffmpeg. No inter-frame prediction. May give better
> > +# Image quality, but a fatter stream.
> 
> image, produces a fatter stream
Done.

> 
> > +# VideoGOPSize: Increasing the value for this increases the amount
> > +# of inter-frame prediction. Setting it very low, will give a better
> 
> s/,//
Done.

> 
> > --- ffserver.conf-3cam-lan-flv	(revision 0)
> > +++ ffserver.conf-3cam-lan-flv	(revision 0)
> > @@ -0,0 +1,145 @@
> > +# Machine was a 1100 Celeron  with 512M RAM.
> 
> MB
Done.

> 
> > +# When dealing with NTSC set frame rate to exactly 29.97 to
> 
> framerate, same below
Done.

> 
> > --- ffserver.conf-swf-flv	(revision 0)
> > +++ ffserver.conf-swf-flv	(revision 0)
> > @@ -0,0 +1,98 @@
> > +VideoBufferSize 128      # adsjust with bitrate, and q.
> 
> adjust
Done.


I tend to capitalize things in these files that are important. There is only so
much one can do to emphasize things in the notes in a conf file. Capitals are
intended to grab the eye and signify importance. Not as important as all-caps,
which is like bold type (or yelling), but important enough to signify.

The other issues raised in response to this submission will be addressed in my
next post.

Thanks.

P.




      ____________________________________________________________________________________
Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/