Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
bcbf8920
Commit
bcbf8920
authored
Nov 28, 2013
by
Stefano Sabatini
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc/ffserver: clarify/extend documentation about status streams
parent
312d075e
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
4 deletions
+5
-4
ffserver.texi
doc/ffserver.texi
+5
-4
No files found.
doc/ffserver.texi
View file @
bcbf8920
...
...
@@ -377,12 +377,13 @@ The following options are recognized within a Stream section.
@item Feed @var
{
feed
_
name
}
Set the input feed.
Must be specified.
Must be specified
for regular streams
.
@item Format @var
{
format
_
name
}
Set the format of the stream.
Set the format of the
output
stream.
Must be the name of a format recognized by FFmpeg.
Must be the name of a format recognized by FFmpeg. If set to
@samp
{
status
}
, it is treated as a status stream.
@item AudioBitRate @var
{
rate
}
Set bitrate for the audio stream in KB per second.
...
...
@@ -482,7 +483,7 @@ A server status stream is a special stream which is used to show
statistics about the @command
{
ffserver
}
operations.
It must be specified setting the option @option
{
Format
}
to
@
code
{
status
}
.
@
samp
{
status
}
.
@section Redirect section
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment