2016-02-11 12:11:48 +00:00
|
|
|
|
@chapter Protocol Options
|
|
|
|
|
@c man begin PROTOCOL OPTIONS
|
|
|
|
|
|
|
|
|
|
The libavformat library provides some generic global options, which
|
|
|
|
|
can be set on all the protocols. In addition each protocol may support
|
|
|
|
|
so-called private options, which are specific for that component.
|
|
|
|
|
|
2017-02-13 21:23:03 +00:00
|
|
|
|
Options may be set by specifying -@var{option} @var{value} in the
|
|
|
|
|
FFmpeg tools, or by setting the value explicitly in the
|
|
|
|
|
@code{AVFormatContext} options or using the @file{libavutil/opt.h} API
|
|
|
|
|
for programmatic use.
|
|
|
|
|
|
2016-02-11 12:11:48 +00:00
|
|
|
|
The list of supported options follows:
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item protocol_whitelist @var{list} (@emph{input})
|
|
|
|
|
Set a ","-separated list of allowed protocols. "ALL" matches all protocols. Protocols
|
|
|
|
|
prefixed by "-" are disabled.
|
|
|
|
|
All protocols are allowed by default but protocols used by an another
|
|
|
|
|
protocol (nested protocols) are restricted to a per protocol subset.
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
@c man end PROTOCOL OPTIONS
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@chapter Protocols
|
|
|
|
|
@c man begin PROTOCOLS
|
|
|
|
|
|
2013-08-10 02:19:53 +00:00
|
|
|
|
Protocols are configured elements in FFmpeg that enable access to
|
|
|
|
|
resources that require specific protocols.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
2011-03-17 15:55:58 +00:00
|
|
|
|
When you configure your FFmpeg build, all the supported protocols are
|
2010-08-06 23:15:35 +00:00
|
|
|
|
enabled by default. You can list all available ones using the
|
|
|
|
|
configure option "--list-protocols".
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
|
|
|
|
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
|
2010-08-06 23:15:35 +00:00
|
|
|
|
supported protocols.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
2012-08-27 13:31:08 +00:00
|
|
|
|
All protocols accept the following options:
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item rw_timeout
|
|
|
|
|
Maximum time to wait for (network) read/write operations to complete,
|
|
|
|
|
in microseconds.
|
|
|
|
|
@end table
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
A description of the currently available protocols follows.
|
|
|
|
|
|
2015-07-16 07:04:42 +00:00
|
|
|
|
@section async
|
|
|
|
|
|
|
|
|
|
Asynchronous data filling wrapper for input stream.
|
|
|
|
|
|
|
|
|
|
Fill data in a background thread, to decouple I/O operation from demux thread.
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
async:@var{URL}
|
|
|
|
|
async:http://host/resource
|
|
|
|
|
async:cache:http://host/resource
|
|
|
|
|
@end example
|
|
|
|
|
|
2012-03-03 03:25:48 +00:00
|
|
|
|
@section bluray
|
|
|
|
|
|
|
|
|
|
Read BluRay playlist.
|
|
|
|
|
|
|
|
|
|
The accepted options are:
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
|
|
@item angle
|
|
|
|
|
BluRay angle
|
|
|
|
|
|
|
|
|
|
@item chapter
|
|
|
|
|
Start chapter (1...N)
|
|
|
|
|
|
|
|
|
|
@item playlist
|
|
|
|
|
Playlist to read (BDMV/PLAYLIST/?????.mpls)
|
|
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
|
|
|
|
|
|
Read longest playlist from BluRay mounted to /mnt/bluray:
|
|
|
|
|
@example
|
|
|
|
|
bluray:/mnt/bluray
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
Read angle 2 of playlist 4 from BluRay mounted to /mnt/bluray, start from chapter 2:
|
|
|
|
|
@example
|
|
|
|
|
-playlist 4 -angle 2 -chapter 2 bluray:/mnt/bluray
|
|
|
|
|
@end example
|
|
|
|
|
|
2013-06-15 20:03:38 +00:00
|
|
|
|
@section cache
|
|
|
|
|
|
|
|
|
|
Caching wrapper for input stream.
|
|
|
|
|
|
2013-06-21 15:40:54 +00:00
|
|
|
|
Cache the input stream to temporary file. It brings seeking capability to live streams.
|
2013-06-15 20:03:38 +00:00
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
cache:@var{URL}
|
|
|
|
|
@end example
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@section concat
|
|
|
|
|
|
|
|
|
|
Physical concatenation protocol.
|
|
|
|
|
|
2015-03-06 19:26:32 +00:00
|
|
|
|
Read and seek from many resources in sequence as if they were
|
2010-08-06 23:15:35 +00:00
|
|
|
|
a unique resource.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
2010-08-07 21:06:46 +00:00
|
|
|
|
A URL accepted by this protocol has the syntax:
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@example
|
|
|
|
|
concat:@var{URL1}|@var{URL2}|...|@var{URLN}
|
|
|
|
|
@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},
|
2012-01-02 14:32:55 +00:00
|
|
|
|
@file{split2.mpeg}, @file{split3.mpeg} with @command{ffplay} use the
|
2010-07-31 15:45:29 +00:00
|
|
|
|
command:
|
|
|
|
|
@example
|
|
|
|
|
ffplay concat:split1.mpeg\|split2.mpeg\|split3.mpeg
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
Note that you may need to escape the character "|" which is special for
|
|
|
|
|
many shells.
|
|
|
|
|
|
2013-06-19 05:17:58 +00:00
|
|
|
|
@section crypto
|
|
|
|
|
|
|
|
|
|
AES-encrypted stream reading protocol.
|
|
|
|
|
|
|
|
|
|
The accepted options are:
|
|
|
|
|
@table @option
|
|
|
|
|
@item key
|
|
|
|
|
Set the AES decryption key binary block from given hexadecimal representation.
|
|
|
|
|
|
|
|
|
|
@item iv
|
|
|
|
|
Set the AES decryption initialization vector binary block from given hexadecimal representation.
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
Accepted URL formats:
|
|
|
|
|
@example
|
|
|
|
|
crypto:@var{URL}
|
|
|
|
|
crypto+@var{URL}
|
|
|
|
|
@end example
|
|
|
|
|
|
2012-12-26 19:26:08 +00:00
|
|
|
|
@section data
|
|
|
|
|
|
|
|
|
|
Data in-line in the URI. See @url{http://en.wikipedia.org/wiki/Data_URI_scheme}.
|
|
|
|
|
|
|
|
|
|
For example, to convert a GIF file given inline with @command{ffmpeg}:
|
|
|
|
|
@example
|
|
|
|
|
ffmpeg -i "data:image/gif;base64,R0lGODdhCAAIAMIEAAAAAAAA//8AAP//AP///////////////ywAAAAACAAIAAADF0gEDLojDgdGiJdJqUX02iB4E8Q9jUMkADs=" smiley.png
|
|
|
|
|
@end example
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@section file
|
|
|
|
|
|
|
|
|
|
File access protocol.
|
|
|
|
|
|
2015-03-06 19:26:32 +00:00
|
|
|
|
Read from or write to a file.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
2014-01-04 13:48:23 +00:00
|
|
|
|
A file URL can have the form:
|
|
|
|
|
@example
|
|
|
|
|
file:@var{filename}
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
where @var{filename} is the path of the file to read.
|
|
|
|
|
|
|
|
|
|
An URL that does not have a protocol prefix will be assumed to be a
|
|
|
|
|
file URL. Depending on the build, an URL that looks like a Windows
|
|
|
|
|
path with the drive letter at the beginning will also be assumed to be
|
|
|
|
|
a file URL (usually not the case in builds for unix-like systems).
|
|
|
|
|
|
2011-12-10 00:25:15 +00:00
|
|
|
|
For example to read from a file @file{input.mpeg} with @command{ffmpeg}
|
2010-07-31 15:45:29 +00:00
|
|
|
|
use the command:
|
|
|
|
|
@example
|
|
|
|
|
ffmpeg -i file:input.mpeg output.mpeg
|
|
|
|
|
@end example
|
|
|
|
|
|
2013-07-14 10:43:25 +00:00
|
|
|
|
This protocol accepts the following options:
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item truncate
|
|
|
|
|
Truncate existing files on write, if set to 1. A value of 0 prevents
|
|
|
|
|
truncating. Default value is 1.
|
|
|
|
|
|
|
|
|
|
@item blocksize
|
|
|
|
|
Set I/O operation maximum block size, in bytes. Default value is
|
|
|
|
|
@code{INT_MAX}, which results in not limiting the requested block size.
|
|
|
|
|
Setting this value reasonably low improves user termination request reaction
|
|
|
|
|
time, which is valuable for files on slow medium.
|
2019-03-03 05:26:48 +00:00
|
|
|
|
|
|
|
|
|
@item follow
|
|
|
|
|
If set to 1, the protocol will retry reading at the end of the file, allowing
|
|
|
|
|
reading files that still are being written. In order for this to terminate,
|
|
|
|
|
you either need to use the rw_timeout option, or use the interrupt callback
|
|
|
|
|
(for API users).
|
2019-04-02 23:13:55 +00:00
|
|
|
|
|
|
|
|
|
@item seekable
|
|
|
|
|
Controls if seekability is advertised on the file. 0 means non-seekable, -1
|
|
|
|
|
means auto (seekable for normal files, non-seekable for named pipes).
|
|
|
|
|
|
|
|
|
|
Many demuxers handle seekable and non-seekable resources differently,
|
|
|
|
|
overriding this might speed up opening certain files at the cost of losing some
|
|
|
|
|
features (e.g. accurate seeking).
|
2013-07-14 10:43:25 +00:00
|
|
|
|
@end table
|
|
|
|
|
|
2013-05-15 14:08:11 +00:00
|
|
|
|
@section ftp
|
|
|
|
|
|
2013-06-21 15:40:54 +00:00
|
|
|
|
FTP (File Transfer Protocol).
|
2013-05-15 14:08:11 +00:00
|
|
|
|
|
2015-03-06 19:26:32 +00:00
|
|
|
|
Read from or write to remote resources using FTP protocol.
|
2013-05-15 14:08:11 +00:00
|
|
|
|
|
|
|
|
|
Following syntax is required.
|
|
|
|
|
@example
|
|
|
|
|
ftp://[user[:password]@@]server[:port]/path/to/remote/resource.mpeg
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
This protocol accepts the following options.
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item timeout
|
2014-07-04 17:58:20 +00:00
|
|
|
|
Set timeout in microseconds of socket I/O operations used by the underlying low level
|
2013-05-15 14:08:11 +00:00
|
|
|
|
operation. By default it is set to -1, which means that the timeout is
|
|
|
|
|
not specified.
|
|
|
|
|
|
2019-10-26 22:37:32 +00:00
|
|
|
|
@item ftp-user
|
|
|
|
|
Set a user to be used for authenticating to the FTP server. This is overridden by the
|
|
|
|
|
user in the FTP URL.
|
|
|
|
|
|
|
|
|
|
@item ftp-password
|
|
|
|
|
Set a password to be used for authenticating to the FTP server. This is overridden by
|
|
|
|
|
the password in the FTP URL, or by @option{ftp-anonymous-password} if no user is set.
|
|
|
|
|
|
2013-05-15 14:08:11 +00:00
|
|
|
|
@item ftp-anonymous-password
|
|
|
|
|
Password used when login as anonymous user. Typically an e-mail address
|
|
|
|
|
should be used.
|
|
|
|
|
|
|
|
|
|
@item ftp-write-seekable
|
|
|
|
|
Control seekability of connection during encoding. If set to 1 the
|
|
|
|
|
resource is supposed to be seekable, if set to 0 it is assumed not
|
|
|
|
|
to be seekable. Default value is 0.
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
NOTE: Protocol can be used as output, but it is recommended to not do
|
|
|
|
|
it, unless special care is taken (tests, customized server configuration
|
|
|
|
|
etc.). Different FTP servers behave in different way during seek
|
|
|
|
|
operation. ff* tools may produce incomplete content due to server limitations.
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@section gopher
|
|
|
|
|
|
|
|
|
|
Gopher protocol.
|
|
|
|
|
|
2012-02-14 10:04:50 +00:00
|
|
|
|
@section hls
|
|
|
|
|
|
|
|
|
|
Read Apple HTTP Live Streaming compliant segmented stream as
|
|
|
|
|
a uniform one. The M3U8 playlists describing the segments can be
|
|
|
|
|
remote HTTP resources or local files, accessed using the standard
|
|
|
|
|
file protocol.
|
|
|
|
|
The nested protocol is declared by specifying
|
|
|
|
|
"+@var{proto}" after the hls URI scheme name, where @var{proto}
|
|
|
|
|
is either "file" or "http".
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
hls+http://host/path/to/remote/resource.m3u8
|
|
|
|
|
hls+file://path/to/local/resource.m3u8
|
|
|
|
|
@end example
|
|
|
|
|
|
2012-02-14 10:09:09 +00:00
|
|
|
|
Using this protocol is discouraged - the hls demuxer should work
|
|
|
|
|
just as well (if not, please report the issues) and is more complete.
|
|
|
|
|
To use the hls demuxer instead, simply use the direct URLs to the
|
|
|
|
|
m3u8 files.
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@section http
|
|
|
|
|
|
2010-08-06 23:15:35 +00:00
|
|
|
|
HTTP (Hyper Text Transfer Protocol).
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
2014-03-10 20:11:35 +00:00
|
|
|
|
This protocol accepts the following options:
|
2013-01-11 10:51:26 +00:00
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item seekable
|
|
|
|
|
Control seekability of connection. If set to 1 the resource is
|
|
|
|
|
supposed to be seekable, if set to 0 it is assumed not to be seekable,
|
2013-01-12 10:01:12 +00:00
|
|
|
|
if set to -1 it will try to autodetect if it is seekable. Default
|
|
|
|
|
value is -1.
|
2013-01-11 10:51:26 +00:00
|
|
|
|
|
|
|
|
|
@item chunked_post
|
2014-03-06 17:40:02 +00:00
|
|
|
|
If set to 1 use chunked Transfer-Encoding for posts, default is 1.
|
2013-01-11 10:51:26 +00:00
|
|
|
|
|
2014-03-06 17:40:03 +00:00
|
|
|
|
@item content_type
|
2016-08-10 19:18:00 +00:00
|
|
|
|
Set a specific content type for the POST messages or for listen mode.
|
2014-03-06 17:40:03 +00:00
|
|
|
|
|
2015-12-28 09:50:15 +00:00
|
|
|
|
@item http_proxy
|
|
|
|
|
set HTTP proxy to tunnel through e.g. http://example.com:1234
|
|
|
|
|
|
2013-01-11 10:51:26 +00:00
|
|
|
|
@item headers
|
|
|
|
|
Set custom HTTP headers, can override built in default headers. The
|
|
|
|
|
value must be a string encoding the headers.
|
|
|
|
|
|
2014-03-06 17:40:02 +00:00
|
|
|
|
@item multiple_requests
|
|
|
|
|
Use persistent connections if set to 1, default is 0.
|
|
|
|
|
|
|
|
|
|
@item post_data
|
|
|
|
|
Set custom HTTP post data.
|
|
|
|
|
|
2018-02-01 02:56:51 +00:00
|
|
|
|
@item referer
|
|
|
|
|
Set the Referer header. Include 'Referer: URL' header in HTTP request.
|
|
|
|
|
|
2014-03-06 17:39:59 +00:00
|
|
|
|
@item user_agent
|
2014-03-12 02:44:23 +00:00
|
|
|
|
Override the User-Agent header. If not specified the protocol will use a
|
|
|
|
|
string describing the libavformat build. ("Lavf/<version>")
|
2013-01-11 10:51:26 +00:00
|
|
|
|
|
2016-09-16 02:42:34 +00:00
|
|
|
|
@item user-agent
|
|
|
|
|
This is a deprecated option, you can use user_agent instead it.
|
|
|
|
|
|
2013-01-11 10:51:26 +00:00
|
|
|
|
@item timeout
|
2014-07-04 17:58:20 +00:00
|
|
|
|
Set timeout in microseconds of socket I/O operations used by the underlying low level
|
2013-01-11 10:51:26 +00:00
|
|
|
|
operation. By default it is set to -1, which means that the timeout is
|
|
|
|
|
not specified.
|
|
|
|
|
|
2015-09-06 17:58:10 +00:00
|
|
|
|
@item reconnect_at_eof
|
2015-09-08 21:42:19 +00:00
|
|
|
|
If set then eof is treated like an error and causes reconnection, this is useful
|
2015-09-06 17:58:10 +00:00
|
|
|
|
for live / endless streams.
|
|
|
|
|
|
|
|
|
|
@item reconnect_streamed
|
|
|
|
|
If set then even streamed/non seekable streams will be reconnected on errors.
|
|
|
|
|
|
2015-09-07 17:38:16 +00:00
|
|
|
|
@item reconnect_delay_max
|
|
|
|
|
Sets the maximum delay in seconds after which to give up reconnecting
|
|
|
|
|
|
2013-01-11 10:51:26 +00:00
|
|
|
|
@item mime_type
|
2014-03-06 17:39:58 +00:00
|
|
|
|
Export the MIME type.
|
2013-01-14 02:33:20 +00:00
|
|
|
|
|
2017-12-26 04:21:15 +00:00
|
|
|
|
@item http_version
|
|
|
|
|
Exports the HTTP response version number. Usually "1.0" or "1.1".
|
|
|
|
|
|
2013-06-25 22:53:26 +00:00
|
|
|
|
@item icy
|
|
|
|
|
If set to 1 request ICY (SHOUTcast) metadata from the server. If the server
|
|
|
|
|
supports this, the metadata has to be retrieved by the application by reading
|
|
|
|
|
the @option{icy_metadata_headers} and @option{icy_metadata_packet} options.
|
2014-07-31 23:56:36 +00:00
|
|
|
|
The default is 1.
|
2013-06-25 22:53:26 +00:00
|
|
|
|
|
|
|
|
|
@item icy_metadata_headers
|
2014-03-10 20:11:35 +00:00
|
|
|
|
If the server supports ICY metadata, this contains the ICY-specific HTTP reply
|
|
|
|
|
headers, separated by newline characters.
|
2013-06-25 22:53:26 +00:00
|
|
|
|
|
|
|
|
|
@item icy_metadata_packet
|
|
|
|
|
If the server supports ICY metadata, and @option{icy} was set to 1, this
|
2014-03-10 20:11:35 +00:00
|
|
|
|
contains the last non-empty metadata packet sent by the server. It should be
|
|
|
|
|
polled in regular intervals by applications interested in mid-stream metadata
|
|
|
|
|
updates.
|
2013-06-25 22:53:26 +00:00
|
|
|
|
|
2013-01-14 02:33:20 +00:00
|
|
|
|
@item cookies
|
|
|
|
|
Set the cookies to be sent in future requests. The format of each cookie is the
|
|
|
|
|
same as the value of a Set-Cookie HTTP response field. Multiple cookies can be
|
|
|
|
|
delimited by a newline character.
|
2014-03-12 03:12:04 +00:00
|
|
|
|
|
2014-03-06 17:40:00 +00:00
|
|
|
|
@item offset
|
|
|
|
|
Set initial byte offset.
|
|
|
|
|
|
|
|
|
|
@item end_offset
|
|
|
|
|
Try to limit the request to bytes preceding this offset.
|
2015-04-02 20:49:07 +00:00
|
|
|
|
|
2015-06-03 23:16:59 +00:00
|
|
|
|
@item method
|
|
|
|
|
When used as a client option it sets the HTTP method for the request.
|
|
|
|
|
|
|
|
|
|
When used as a server option it sets the HTTP method that is going to be
|
|
|
|
|
expected from the client(s).
|
|
|
|
|
If the expected and the received HTTP method do not match the client will
|
|
|
|
|
be given a Bad Request response.
|
|
|
|
|
When unset the HTTP method is not checked for now. This will be replaced by
|
|
|
|
|
autodetection in the future.
|
|
|
|
|
|
2015-04-02 20:49:07 +00:00
|
|
|
|
@item listen
|
2015-04-11 20:26:57 +00:00
|
|
|
|
If set to 1 enables experimental HTTP server. This can be used to send data when
|
|
|
|
|
used as an output option, or read data from a client with HTTP POST when used as
|
|
|
|
|
an input option.
|
2016-10-09 18:51:57 +00:00
|
|
|
|
If set to 2 enables experimental multi-client HTTP server. This is not yet implemented
|
2017-10-21 18:31:44 +00:00
|
|
|
|
in ffmpeg.c and thus must not be used as a command line option.
|
2015-04-11 20:26:57 +00:00
|
|
|
|
@example
|
|
|
|
|
# Server side (sending):
|
|
|
|
|
ffmpeg -i somefile.ogg -c copy -listen 1 -f ogg http://@var{server}:@var{port}
|
|
|
|
|
|
|
|
|
|
# Client side (receiving):
|
|
|
|
|
ffmpeg -i http://@var{server}:@var{port} -c copy somefile.ogg
|
|
|
|
|
|
|
|
|
|
# Client can also be done with wget:
|
|
|
|
|
wget http://@var{server}:@var{port} -O somefile.ogg
|
|
|
|
|
|
|
|
|
|
# Server side (receiving):
|
|
|
|
|
ffmpeg -listen 1 -i http://@var{server}:@var{port} -c copy somefile.ogg
|
|
|
|
|
|
|
|
|
|
# Client side (sending):
|
|
|
|
|
ffmpeg -i somefile.ogg -chunked_post 0 -c copy -f ogg http://@var{server}:@var{port}
|
|
|
|
|
|
|
|
|
|
# Client can also be done with wget:
|
|
|
|
|
wget --post-file=somefile.ogg http://@var{server}:@var{port}
|
|
|
|
|
@end example
|
|
|
|
|
|
2019-03-31 04:35:51 +00:00
|
|
|
|
@item send_expect_100
|
|
|
|
|
Send an Expect: 100-continue header for POST. If set to 1 it will send, if set
|
|
|
|
|
to 0 it won't, if set to -1 it will try to send if it is applicable. Default
|
|
|
|
|
value is -1.
|
|
|
|
|
|
2013-01-11 10:51:26 +00:00
|
|
|
|
@end table
|
|
|
|
|
|
2013-01-14 02:33:20 +00:00
|
|
|
|
@subsection HTTP Cookies
|
|
|
|
|
|
|
|
|
|
Some HTTP requests will be denied unless cookie values are passed in with the
|
|
|
|
|
request. The @option{cookies} option allows these cookies to be specified. At
|
|
|
|
|
the very least, each cookie must specify a value along with a path and domain.
|
|
|
|
|
HTTP requests that match both the domain and path will automatically include the
|
|
|
|
|
cookie value in the HTTP Cookie header field. Multiple cookies can be delimited
|
|
|
|
|
by a newline.
|
|
|
|
|
|
|
|
|
|
The required syntax to play a stream specifying a cookie is:
|
|
|
|
|
@example
|
|
|
|
|
ffplay -cookies "nlqptid=nltid=tsn; path=/; domain=somedomain.com;" http://somedomain.com/somestream.m3u8
|
|
|
|
|
@end example
|
|
|
|
|
|
2014-07-28 08:36:19 +00:00
|
|
|
|
@section Icecast
|
|
|
|
|
|
2014-08-04 12:13:45 +00:00
|
|
|
|
Icecast protocol (stream to Icecast servers)
|
2014-07-28 09:55:38 +00:00
|
|
|
|
|
|
|
|
|
This protocol accepts the following options:
|
2014-07-28 08:36:19 +00:00
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item ice_genre
|
2014-07-28 09:55:38 +00:00
|
|
|
|
Set the stream genre.
|
2014-07-28 08:36:19 +00:00
|
|
|
|
|
|
|
|
|
@item ice_name
|
2014-07-28 09:55:38 +00:00
|
|
|
|
Set the stream name.
|
2014-07-28 08:36:19 +00:00
|
|
|
|
|
|
|
|
|
@item ice_description
|
2014-07-28 09:55:38 +00:00
|
|
|
|
Set the stream description.
|
2014-07-28 08:36:19 +00:00
|
|
|
|
|
|
|
|
|
@item ice_url
|
2014-07-28 09:55:38 +00:00
|
|
|
|
Set the stream website URL.
|
2014-07-28 08:36:19 +00:00
|
|
|
|
|
|
|
|
|
@item ice_public
|
|
|
|
|
Set if the stream should be public.
|
2014-07-28 09:55:38 +00:00
|
|
|
|
The default is 0 (not public).
|
2014-07-28 08:36:19 +00:00
|
|
|
|
|
2014-07-28 09:55:38 +00:00
|
|
|
|
@item user_agent
|
|
|
|
|
Override the User-Agent header. If not specified a string of the form
|
|
|
|
|
"Lavf/<version>" will be used.
|
2014-07-28 08:36:19 +00:00
|
|
|
|
|
2014-07-28 09:55:38 +00:00
|
|
|
|
@item password
|
|
|
|
|
Set the Icecast mountpoint password.
|
2014-07-28 08:36:19 +00:00
|
|
|
|
|
|
|
|
|
@item content_type
|
2014-07-28 09:55:38 +00:00
|
|
|
|
Set the stream content type. This must be set if it is different from
|
|
|
|
|
audio/mpeg.
|
2014-07-28 08:36:19 +00:00
|
|
|
|
|
2014-07-28 09:55:38 +00:00
|
|
|
|
@item legacy_icecast
|
|
|
|
|
This enables support for Icecast versions < 2.4.0, that do not support the
|
|
|
|
|
HTTP PUT method but the SOURCE method.
|
2014-07-28 08:36:19 +00:00
|
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
icecast://[@var{username}[:@var{password}]@@]@var{server}:@var{port}/@var{mountpoint}
|
|
|
|
|
@end example
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@section mmst
|
|
|
|
|
|
|
|
|
|
MMS (Microsoft Media Server) protocol over TCP.
|
|
|
|
|
|
2010-08-21 19:04:41 +00:00
|
|
|
|
@section mmsh
|
|
|
|
|
|
|
|
|
|
MMS (Microsoft Media Server) protocol over HTTP.
|
|
|
|
|
|
|
|
|
|
The required syntax is:
|
|
|
|
|
@example
|
|
|
|
|
mmsh://@var{server}[:@var{port}][/@var{app}][/@var{playpath}]
|
|
|
|
|
@end example
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@section md5
|
|
|
|
|
|
|
|
|
|
MD5 output protocol.
|
|
|
|
|
|
2010-08-06 23:15:35 +00:00
|
|
|
|
Computes the MD5 hash of the data to be 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.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
|
|
|
|
Some examples follow.
|
|
|
|
|
@example
|
2010-08-07 21:06:46 +00:00
|
|
|
|
# Write the MD5 hash of the encoded AVI file to the file output.avi.md5.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
ffmpeg -i input.flv -f avi -y md5:output.avi.md5
|
|
|
|
|
|
2010-08-06 23:15:35 +00:00
|
|
|
|
# Write the MD5 hash of the encoded AVI file to stdout.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
ffmpeg -i input.flv -f avi -y md5:
|
|
|
|
|
@end example
|
|
|
|
|
|
2010-08-06 23:15:35 +00:00
|
|
|
|
Note that some formats (typically MOV) require the output protocol to
|
2010-07-31 15:45:29 +00:00
|
|
|
|
be seekable, so they will fail with the MD5 output protocol.
|
|
|
|
|
|
|
|
|
|
@section pipe
|
|
|
|
|
|
|
|
|
|
UNIX pipe access protocol.
|
|
|
|
|
|
2015-03-06 19:26:32 +00:00
|
|
|
|
Read and write from UNIX pipes.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
|
|
|
|
The accepted syntax is:
|
|
|
|
|
@example
|
|
|
|
|
pipe:[@var{number}]
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
@var{number} is the number corresponding to the file descriptor of the
|
2010-08-06 23:15:35 +00:00
|
|
|
|
pipe (e.g. 0 for stdin, 1 for stdout, 2 for stderr). If @var{number}
|
|
|
|
|
is not specified, by default the stdout file descriptor will be used
|
|
|
|
|
for writing, stdin for reading.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
2011-12-10 00:25:15 +00:00
|
|
|
|
For example to read from stdin with @command{ffmpeg}:
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@example
|
|
|
|
|
cat test.wav | ffmpeg -i pipe:0
|
2010-08-06 23:15:35 +00:00
|
|
|
|
# ...this is the same as...
|
2010-07-31 15:45:29 +00:00
|
|
|
|
cat test.wav | ffmpeg -i pipe:
|
|
|
|
|
@end example
|
|
|
|
|
|
2011-12-10 00:25:15 +00:00
|
|
|
|
For writing to stdout with @command{ffmpeg}:
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@example
|
|
|
|
|
ffmpeg -i test.wav -f avi pipe:1 | cat > test.avi
|
2010-08-06 23:15:35 +00:00
|
|
|
|
# ...this is the same as...
|
2010-07-31 15:45:29 +00:00
|
|
|
|
ffmpeg -i test.wav -f avi pipe: | cat > test.avi
|
|
|
|
|
@end example
|
|
|
|
|
|
2013-07-31 12:22:02 +00:00
|
|
|
|
This protocol accepts the following options:
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item blocksize
|
|
|
|
|
Set I/O operation maximum block size, in bytes. Default value is
|
|
|
|
|
@code{INT_MAX}, which results in not limiting the requested block size.
|
|
|
|
|
Setting this value reasonably low improves user termination request reaction
|
|
|
|
|
time, which is valuable if data transmission is slow.
|
|
|
|
|
@end table
|
|
|
|
|
|
2010-08-06 23:15:35 +00:00
|
|
|
|
Note that some formats (typically MOV), require the output protocol to
|
2010-07-31 15:45:29 +00:00
|
|
|
|
be seekable, so they will fail with the pipe output protocol.
|
|
|
|
|
|
2016-06-02 14:28:13 +00:00
|
|
|
|
@section prompeg
|
|
|
|
|
|
|
|
|
|
Pro-MPEG Code of Practice #3 Release 2 FEC protocol.
|
|
|
|
|
|
|
|
|
|
The Pro-MPEG CoP#3 FEC is a 2D parity-check forward error correction mechanism
|
|
|
|
|
for MPEG-2 Transport Streams sent over RTP.
|
|
|
|
|
|
|
|
|
|
This protocol must be used in conjunction with the @code{rtp_mpegts} muxer and
|
|
|
|
|
the @code{rtp} protocol.
|
|
|
|
|
|
|
|
|
|
The required syntax is:
|
|
|
|
|
@example
|
|
|
|
|
-f rtp_mpegts -fec prompeg=@var{option}=@var{val}... rtp://@var{hostname}:@var{port}
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
The destination UDP ports are @code{port + 2} for the column FEC stream
|
|
|
|
|
and @code{port + 4} for the row FEC stream.
|
|
|
|
|
|
|
|
|
|
This protocol accepts the following options:
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
|
|
@item l=@var{n}
|
|
|
|
|
The number of columns (4-20, LxD <= 100)
|
|
|
|
|
|
|
|
|
|
@item d=@var{n}
|
|
|
|
|
The number of rows (4-20, LxD <= 100)
|
|
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
Example usage:
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
-f rtp_mpegts -fec prompeg=l=8:d=4 rtp://@var{hostname}:@var{port}
|
|
|
|
|
@end example
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@section rtmp
|
|
|
|
|
|
|
|
|
|
Real-Time Messaging Protocol.
|
|
|
|
|
|
2011-10-05 12:12:42 +00:00
|
|
|
|
The Real-Time Messaging Protocol (RTMP) is used for streaming multimedia
|
|
|
|
|
content across a TCP/IP network.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
|
|
|
|
The required syntax is:
|
|
|
|
|
@example
|
2013-08-10 08:51:31 +00:00
|
|
|
|
rtmp://[@var{username}:@var{password}@@]@var{server}[:@var{port}][/@var{app}][/@var{instance}][/@var{playpath}]
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@end example
|
|
|
|
|
|
2010-08-06 23:15:35 +00:00
|
|
|
|
The accepted parameters are:
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@table @option
|
|
|
|
|
|
2013-08-10 08:51:31 +00:00
|
|
|
|
@item username
|
|
|
|
|
An optional username (mostly for publishing).
|
|
|
|
|
|
|
|
|
|
@item password
|
|
|
|
|
An optional password (mostly for publishing).
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@item server
|
2010-08-06 23:15:35 +00:00
|
|
|
|
The address of the RTMP server.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
|
|
|
|
@item port
|
2010-08-06 23:15:35 +00:00
|
|
|
|
The number of the TCP port to use (by default is 1935).
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
|
|
|
|
@item app
|
2010-08-06 23:15:35 +00:00
|
|
|
|
It is the name of the application to access. It usually corresponds to
|
|
|
|
|
the path where the application is installed on the RTMP server
|
2012-06-08 11:15:21 +00:00
|
|
|
|
(e.g. @file{/ondemand/}, @file{/flash/live/}, etc.). You can override
|
|
|
|
|
the value parsed from the URI through the @code{rtmp_app} option, too.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
|
|
|
|
@item playpath
|
|
|
|
|
It is the path or name of the resource to play with reference to the
|
2012-06-08 11:15:21 +00:00
|
|
|
|
application specified in @var{app}, may be prefixed by "mp4:". You
|
|
|
|
|
can override the value parsed from the URI through the @code{rtmp_playpath}
|
|
|
|
|
option, too.
|
|
|
|
|
|
2012-08-16 14:04:48 +00:00
|
|
|
|
@item listen
|
|
|
|
|
Act as a server, listening for an incoming connection.
|
|
|
|
|
|
|
|
|
|
@item timeout
|
|
|
|
|
Maximum time to wait for the incoming connection. Implies listen.
|
2012-06-08 11:15:21 +00:00
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
Additionally, the following parameters can be set via command line options
|
|
|
|
|
(or in code via @code{AVOption}s):
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
|
|
@item rtmp_app
|
|
|
|
|
Name of application to connect on the RTMP server. This option
|
|
|
|
|
overrides the parameter specified in the URI.
|
|
|
|
|
|
2012-06-13 13:02:03 +00:00
|
|
|
|
@item rtmp_buffer
|
|
|
|
|
Set the client buffer time in milliseconds. The default is 3000.
|
|
|
|
|
|
2012-06-08 11:16:34 +00:00
|
|
|
|
@item rtmp_conn
|
|
|
|
|
Extra arbitrary AMF connection parameters, parsed from a string,
|
|
|
|
|
e.g. like @code{B:1 S:authMe O:1 NN:code:1.23 NS:flag:ok O:0}.
|
|
|
|
|
Each value is prefixed by a single character denoting the type,
|
|
|
|
|
B for Boolean, N for number, S for string, O for object, or Z for null,
|
|
|
|
|
followed by a colon. For Booleans the data must be either 0 or 1 for
|
|
|
|
|
FALSE or TRUE, respectively. Likewise for Objects the data must be 0 or
|
|
|
|
|
1 to end or begin an object, respectively. Data items in subobjects may
|
|
|
|
|
be named, by prefixing the type with 'N' and specifying the name before
|
|
|
|
|
the value (i.e. @code{NB:myFlag:1}). This option may be used multiple
|
|
|
|
|
times to construct arbitrary AMF sequences.
|
|
|
|
|
|
2012-06-08 11:15:21 +00:00
|
|
|
|
@item rtmp_flashver
|
|
|
|
|
Version of the Flash plugin used to run the SWF player. The default
|
2013-08-10 08:51:49 +00:00
|
|
|
|
is LNX 9,0,124,2. (When publishing, the default is FMLE/3.0 (compatible;
|
|
|
|
|
<libavformat version>).)
|
2012-06-08 11:15:21 +00:00
|
|
|
|
|
2012-06-18 12:55:55 +00:00
|
|
|
|
@item rtmp_flush_interval
|
|
|
|
|
Number of packets flushed in the same request (RTMPT only). The default
|
|
|
|
|
is 10.
|
|
|
|
|
|
2012-06-08 11:15:21 +00:00
|
|
|
|
@item rtmp_live
|
|
|
|
|
Specify that the media is a live stream. No resuming or seeking in
|
|
|
|
|
live streams is possible. The default value is @code{any}, which means the
|
|
|
|
|
subscriber first tries to play the live stream specified in the
|
|
|
|
|
playpath. If a live stream of that name is not found, it plays the
|
|
|
|
|
recorded stream. The other possible values are @code{live} and
|
|
|
|
|
@code{recorded}.
|
|
|
|
|
|
2012-07-24 14:29:40 +00:00
|
|
|
|
@item rtmp_pageurl
|
|
|
|
|
URL of the web page in which the media was embedded. By default no
|
|
|
|
|
value will be sent.
|
|
|
|
|
|
2012-06-08 11:15:21 +00:00
|
|
|
|
@item rtmp_playpath
|
|
|
|
|
Stream identifier to play or to publish. This option overrides the
|
|
|
|
|
parameter specified in the URI.
|
|
|
|
|
|
2012-08-07 20:02:27 +00:00
|
|
|
|
@item rtmp_subscribe
|
|
|
|
|
Name of live stream to subscribe to. By default no value will be sent.
|
|
|
|
|
It is only sent if the option is specified or if rtmp_live
|
|
|
|
|
is set to live.
|
|
|
|
|
|
2012-08-13 15:05:00 +00:00
|
|
|
|
@item rtmp_swfhash
|
|
|
|
|
SHA256 hash of the decompressed SWF file (32 bytes).
|
|
|
|
|
|
|
|
|
|
@item rtmp_swfsize
|
|
|
|
|
Size of the decompressed SWF file, required for SWFVerification.
|
|
|
|
|
|
2012-06-08 11:15:21 +00:00
|
|
|
|
@item rtmp_swfurl
|
|
|
|
|
URL of the SWF player for the media. By default no value will be sent.
|
|
|
|
|
|
2012-08-15 14:11:50 +00:00
|
|
|
|
@item rtmp_swfverify
|
|
|
|
|
URL to player swf file, compute hash/size automatically.
|
|
|
|
|
|
2012-06-08 11:15:21 +00:00
|
|
|
|
@item rtmp_tcurl
|
2012-07-24 14:29:39 +00:00
|
|
|
|
URL of the target stream. Defaults to proto://host[:port]/app.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
2012-01-02 14:32:55 +00:00
|
|
|
|
For example to read with @command{ffplay} a multimedia resource named
|
2010-07-31 15:45:29 +00:00
|
|
|
|
"sample" from the application "vod" from an RTMP server "myserver":
|
|
|
|
|
@example
|
|
|
|
|
ffplay rtmp://myserver/vod/sample
|
|
|
|
|
@end example
|
|
|
|
|
|
2013-08-10 09:08:43 +00:00
|
|
|
|
To publish to a password protected server, passing the playpath and
|
|
|
|
|
app names separately:
|
|
|
|
|
@example
|
2013-08-11 09:33:49 +00:00
|
|
|
|
ffmpeg -re -i <input> -f flv -rtmp_playpath some/long/path -rtmp_app long/app/name rtmp://username:password@@myserver/
|
2013-08-10 09:08:43 +00:00
|
|
|
|
@end example
|
|
|
|
|
|
2012-07-19 12:13:58 +00:00
|
|
|
|
@section rtmpe
|
|
|
|
|
|
|
|
|
|
Encrypted Real-Time Messaging Protocol.
|
|
|
|
|
|
|
|
|
|
The Encrypted Real-Time Messaging Protocol (RTMPE) is used for
|
|
|
|
|
streaming multimedia content within standard cryptographic primitives,
|
|
|
|
|
consisting of Diffie-Hellman key exchange and HMACSHA256, generating
|
|
|
|
|
a pair of RC4 keys.
|
|
|
|
|
|
2012-07-17 10:02:42 +00:00
|
|
|
|
@section rtmps
|
|
|
|
|
|
|
|
|
|
Real-Time Messaging Protocol over a secure SSL connection.
|
|
|
|
|
|
|
|
|
|
The Real-Time Messaging Protocol (RTMPS) is used for streaming
|
|
|
|
|
multimedia content across an encrypted connection.
|
|
|
|
|
|
2012-06-17 18:24:43 +00:00
|
|
|
|
@section rtmpt
|
|
|
|
|
|
|
|
|
|
Real-Time Messaging Protocol tunneled through HTTP.
|
|
|
|
|
|
|
|
|
|
The Real-Time Messaging Protocol tunneled through HTTP (RTMPT) is used
|
|
|
|
|
for streaming multimedia content within HTTP requests to traverse
|
|
|
|
|
firewalls.
|
|
|
|
|
|
2012-07-20 14:36:47 +00:00
|
|
|
|
@section rtmpte
|
|
|
|
|
|
|
|
|
|
Encrypted Real-Time Messaging Protocol tunneled through HTTP.
|
|
|
|
|
|
|
|
|
|
The Encrypted Real-Time Messaging Protocol tunneled through HTTP (RTMPTE)
|
|
|
|
|
is used for streaming multimedia content within HTTP requests to traverse
|
|
|
|
|
firewalls.
|
|
|
|
|
|
2012-07-17 10:02:43 +00:00
|
|
|
|
@section rtmpts
|
|
|
|
|
|
|
|
|
|
Real-Time Messaging Protocol tunneled through HTTPS.
|
|
|
|
|
|
|
|
|
|
The Real-Time Messaging Protocol tunneled through HTTPS (RTMPTS) is used
|
|
|
|
|
for streaming multimedia content within HTTPS requests to traverse
|
|
|
|
|
firewalls.
|
|
|
|
|
|
2014-07-12 22:54:23 +00:00
|
|
|
|
@section libsmbclient
|
|
|
|
|
|
2014-07-20 21:34:57 +00:00
|
|
|
|
libsmbclient permits one to manipulate CIFS/SMB network resources.
|
2014-07-12 22:54:23 +00:00
|
|
|
|
|
|
|
|
|
Following syntax is required.
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
smb://[[domain:]user[:password@@]]server[/share[/path[/file]]]
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
This protocol accepts the following options.
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item timeout
|
2016-07-17 16:10:27 +00:00
|
|
|
|
Set timeout in milliseconds of socket I/O operations used by the underlying
|
2014-07-12 22:54:23 +00:00
|
|
|
|
low level operation. By default it is set to -1, which means that the timeout
|
|
|
|
|
is not specified.
|
|
|
|
|
|
|
|
|
|
@item truncate
|
|
|
|
|
Truncate existing files on write, if set to 1. A value of 0 prevents
|
|
|
|
|
truncating. Default value is 1.
|
|
|
|
|
|
|
|
|
|
@item workgroup
|
|
|
|
|
Set the workgroup used for making connections. By default workgroup is not specified.
|
|
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
For more information see: @url{http://www.samba.org/}.
|
|
|
|
|
|
2013-09-18 12:08:11 +00:00
|
|
|
|
@section libssh
|
|
|
|
|
|
|
|
|
|
Secure File Transfer Protocol via libssh
|
|
|
|
|
|
2015-03-06 19:26:32 +00:00
|
|
|
|
Read from or write to remote resources using SFTP protocol.
|
2013-09-18 12:08:11 +00:00
|
|
|
|
|
|
|
|
|
Following syntax is required.
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
sftp://[user[:password]@@]server[:port]/path/to/remote/resource.mpeg
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
This protocol accepts the following options.
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item timeout
|
|
|
|
|
Set timeout of socket I/O operations used by the underlying low level
|
|
|
|
|
operation. By default it is set to -1, which means that the timeout
|
|
|
|
|
is not specified.
|
|
|
|
|
|
|
|
|
|
@item truncate
|
|
|
|
|
Truncate existing files on write, if set to 1. A value of 0 prevents
|
|
|
|
|
truncating. Default value is 1.
|
|
|
|
|
|
2014-01-20 21:57:57 +00:00
|
|
|
|
@item private_key
|
|
|
|
|
Specify the path of the file containing private key to use during authorization.
|
|
|
|
|
By default libssh searches for keys in the @file{~/.ssh/} directory.
|
|
|
|
|
|
2013-09-18 12:08:11 +00:00
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
Example: Play a file stored on remote server.
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
ffplay sftp://user:password@@server_address:22/home/user/resource.mpeg
|
|
|
|
|
@end example
|
|
|
|
|
|
2013-08-10 09:03:54 +00:00
|
|
|
|
@section librtmp rtmp, rtmpe, rtmps, rtmpt, rtmpte
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
|
|
|
|
Real-Time Messaging Protocol and its variants supported through
|
|
|
|
|
librtmp.
|
|
|
|
|
|
2010-08-06 23:15:35 +00:00
|
|
|
|
Requires the presence of the librtmp headers and library during
|
2011-11-29 16:54:49 +00:00
|
|
|
|
configuration. You need to explicitly configure the build with
|
2010-07-31 15:45:29 +00:00
|
|
|
|
"--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:
|
|
|
|
|
@example
|
|
|
|
|
@var{rtmp_proto}://@var{server}[:@var{port}][/@var{app}][/@var{playpath}] @var{options}
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
where @var{rtmp_proto} is one of the strings "rtmp", "rtmpt", "rtmpe",
|
|
|
|
|
"rtmps", "rtmpte", "rtmpts" corresponding to each RTMP variant, and
|
|
|
|
|
@var{server}, @var{port}, @var{app} and @var{playpath} have the same
|
2010-08-06 23:15:35 +00:00
|
|
|
|
meaning as specified for the RTMP native protocol.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@var{options} contains a list of space-separated options of the form
|
|
|
|
|
@var{key}=@var{val}.
|
|
|
|
|
|
2010-08-06 23:15:35 +00:00
|
|
|
|
See the librtmp manual page (man 3 librtmp) for more information.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
|
|
|
|
For example, to stream a file in real-time to an RTMP server using
|
2011-12-10 00:25:15 +00:00
|
|
|
|
@command{ffmpeg}:
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@example
|
|
|
|
|
ffmpeg -re -i myfile -f flv rtmp://myserver/live/mystream
|
|
|
|
|
@end example
|
|
|
|
|
|
2012-01-02 14:32:55 +00:00
|
|
|
|
To play the same stream using @command{ffplay}:
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@example
|
|
|
|
|
ffplay "rtmp://myserver/live/mystream live=1"
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
@section rtp
|
|
|
|
|
|
2013-10-27 11:39:21 +00:00
|
|
|
|
Real-time Transport Protocol.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
2013-10-24 09:37:57 +00:00
|
|
|
|
The required syntax for an RTP URL is:
|
|
|
|
|
rtp://@var{hostname}[:@var{port}][?@var{option}=@var{val}...]
|
|
|
|
|
|
|
|
|
|
@var{port} specifies the RTP port to use.
|
|
|
|
|
|
|
|
|
|
The following URL options are supported:
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
|
|
@item ttl=@var{n}
|
2013-10-27 11:39:21 +00:00
|
|
|
|
Set the TTL (Time-To-Live) value (for multicast only).
|
2013-10-24 09:37:57 +00:00
|
|
|
|
|
|
|
|
|
@item rtcpport=@var{n}
|
|
|
|
|
Set the remote RTCP port to @var{n}.
|
|
|
|
|
|
|
|
|
|
@item localrtpport=@var{n}
|
|
|
|
|
Set the local RTP port to @var{n}.
|
|
|
|
|
|
|
|
|
|
@item localrtcpport=@var{n}'
|
|
|
|
|
Set the local RTCP port to @var{n}.
|
|
|
|
|
|
|
|
|
|
@item pkt_size=@var{n}
|
|
|
|
|
Set max packet size (in bytes) to @var{n}.
|
|
|
|
|
|
|
|
|
|
@item connect=0|1
|
|
|
|
|
Do a @code{connect()} on the UDP socket (if set to 1) or not (if set
|
|
|
|
|
to 0).
|
|
|
|
|
|
|
|
|
|
@item sources=@var{ip}[,@var{ip}]
|
|
|
|
|
List allowed source IP addresses.
|
|
|
|
|
|
|
|
|
|
@item block=@var{ip}[,@var{ip}]
|
|
|
|
|
List disallowed (blocked) source IP addresses.
|
|
|
|
|
|
|
|
|
|
@item write_to_source=0|1
|
|
|
|
|
Send packets to the source address of the latest received packet (if
|
|
|
|
|
set to 1) or to a default remote address (if set to 0).
|
|
|
|
|
|
2013-10-27 11:39:21 +00:00
|
|
|
|
@item localport=@var{n}
|
|
|
|
|
Set the local RTP port to @var{n}.
|
|
|
|
|
|
|
|
|
|
This is a deprecated option. Instead, @option{localrtpport} should be
|
|
|
|
|
used.
|
2013-10-24 09:37:57 +00:00
|
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
Important notes:
|
|
|
|
|
|
|
|
|
|
@enumerate
|
|
|
|
|
|
|
|
|
|
@item
|
2013-10-27 11:39:21 +00:00
|
|
|
|
If @option{rtcpport} is not set the RTCP port will be set to the RTP
|
2013-10-24 09:37:57 +00:00
|
|
|
|
port value plus 1.
|
|
|
|
|
|
|
|
|
|
@item
|
2013-10-27 11:39:21 +00:00
|
|
|
|
If @option{localrtpport} (the local RTP port) is not set any available
|
2013-10-24 09:37:57 +00:00
|
|
|
|
port will be used for the local RTP and RTCP ports.
|
|
|
|
|
|
|
|
|
|
@item
|
|
|
|
|
If @option{localrtcpport} (the local RTCP port) is not set it will be
|
2014-11-22 01:09:09 +00:00
|
|
|
|
set to the local RTP port value plus 1.
|
2013-10-24 09:37:57 +00:00
|
|
|
|
@end enumerate
|
|
|
|
|
|
2010-10-04 07:06:58 +00:00
|
|
|
|
@section rtsp
|
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
Real-Time Streaming Protocol.
|
|
|
|
|
|
2010-10-04 07:06:58 +00:00
|
|
|
|
RTSP is not technically a protocol handler in libavformat, it is a demuxer
|
|
|
|
|
and muxer. The demuxer supports both normal RTSP (with data transferred
|
|
|
|
|
over RTP; this is used by e.g. Apple and Microsoft) and Real-RTSP (with
|
|
|
|
|
data transferred over RDT).
|
|
|
|
|
|
|
|
|
|
The muxer can be used to send a stream using RTSP ANNOUNCE to a server
|
|
|
|
|
supporting it (currently Darwin Streaming Server and Mischa Spiegelmock's
|
2014-03-12 22:03:11 +00:00
|
|
|
|
@uref{https://github.com/revmischa/rtsp-server, RTSP server}).
|
2010-10-04 07:06:58 +00:00
|
|
|
|
|
|
|
|
|
The required syntax for a RTSP url is:
|
|
|
|
|
@example
|
2011-10-12 15:27:18 +00:00
|
|
|
|
rtsp://@var{hostname}[:@var{port}]/@var{path}
|
2010-10-04 07:06:58 +00:00
|
|
|
|
@end example
|
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
Options can be set on the @command{ffmpeg}/@command{ffplay} command
|
|
|
|
|
line, or set in code via @code{AVOption}s or in
|
|
|
|
|
@code{avformat_open_input}.
|
2010-10-04 07:06:58 +00:00
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
The following options are supported.
|
2011-10-12 15:27:18 +00:00
|
|
|
|
|
2010-10-04 07:06:58 +00:00
|
|
|
|
@table @option
|
2013-12-29 15:43:48 +00:00
|
|
|
|
@item initial_pause
|
|
|
|
|
Do not start playing the stream immediately if set to 1. Default value
|
|
|
|
|
is 0.
|
2010-10-04 07:06:58 +00:00
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
@item rtsp_transport
|
2014-06-20 08:16:01 +00:00
|
|
|
|
Set RTSP transport protocols.
|
2013-12-29 15:43:48 +00:00
|
|
|
|
|
|
|
|
|
It accepts the following values:
|
|
|
|
|
@table @samp
|
2010-10-04 07:06:58 +00:00
|
|
|
|
@item udp
|
|
|
|
|
Use UDP as lower transport protocol.
|
|
|
|
|
|
|
|
|
|
@item tcp
|
|
|
|
|
Use TCP (interleaving within the RTSP control channel) as lower
|
|
|
|
|
transport protocol.
|
|
|
|
|
|
2011-10-12 15:27:18 +00:00
|
|
|
|
@item udp_multicast
|
2010-10-04 07:06:58 +00:00
|
|
|
|
Use UDP multicast as lower transport protocol.
|
|
|
|
|
|
|
|
|
|
@item http
|
|
|
|
|
Use HTTP tunneling as lower transport protocol, which is useful for
|
|
|
|
|
passing proxies.
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
Multiple lower transport protocols may be specified, in that case they are
|
|
|
|
|
tried one at a time (if the setup of one fails, the next one is tried).
|
2013-12-29 15:43:48 +00:00
|
|
|
|
For the muxer, only the @samp{tcp} and @samp{udp} options are supported.
|
2010-10-04 07:06:58 +00:00
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
@item rtsp_flags
|
|
|
|
|
Set RTSP flags.
|
2011-10-12 15:27:18 +00:00
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
The following values are accepted:
|
|
|
|
|
@table @samp
|
2011-10-12 15:27:18 +00:00
|
|
|
|
@item filter_src
|
|
|
|
|
Accept packets only from negotiated peer address and port.
|
2012-07-10 17:36:11 +00:00
|
|
|
|
@item listen
|
|
|
|
|
Act as a server, listening for an incoming connection.
|
2014-03-04 13:43:59 +00:00
|
|
|
|
@item prefer_tcp
|
|
|
|
|
Try TCP for RTP transport first, if TCP is available as RTSP RTP transport.
|
2011-10-12 15:27:18 +00:00
|
|
|
|
@end table
|
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
Default value is @samp{none}.
|
|
|
|
|
|
|
|
|
|
@item allowed_media_types
|
|
|
|
|
Set media types to accept from the server.
|
|
|
|
|
|
|
|
|
|
The following flags are accepted:
|
|
|
|
|
@table @samp
|
|
|
|
|
@item video
|
|
|
|
|
@item audio
|
|
|
|
|
@item data
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
By default it accepts all media types.
|
|
|
|
|
|
|
|
|
|
@item min_port
|
|
|
|
|
Set minimum local UDP port. Default value is 5000.
|
|
|
|
|
|
|
|
|
|
@item max_port
|
|
|
|
|
Set maximum local UDP port. Default value is 65000.
|
|
|
|
|
|
|
|
|
|
@item timeout
|
|
|
|
|
Set maximum timeout (in seconds) to wait for incoming connections.
|
|
|
|
|
|
2014-06-20 08:16:01 +00:00
|
|
|
|
A value of -1 means infinite (default). This option implies the
|
2013-12-29 15:43:48 +00:00
|
|
|
|
@option{rtsp_flags} set to @samp{listen}.
|
|
|
|
|
|
|
|
|
|
@item reorder_queue_size
|
|
|
|
|
Set number of packets to buffer for handling of reordered packets.
|
|
|
|
|
|
|
|
|
|
@item stimeout
|
2014-06-20 08:16:01 +00:00
|
|
|
|
Set socket TCP I/O timeout in microseconds.
|
2013-12-29 15:43:48 +00:00
|
|
|
|
|
|
|
|
|
@item user-agent
|
2014-06-20 08:16:01 +00:00
|
|
|
|
Override User-Agent header. If not specified, it defaults to the
|
2013-12-29 15:43:48 +00:00
|
|
|
|
libavformat identifier string.
|
|
|
|
|
@end table
|
|
|
|
|
|
2010-10-04 07:06:58 +00:00
|
|
|
|
When receiving data over UDP, the demuxer tries to reorder received packets
|
2012-03-19 18:40:23 +00:00
|
|
|
|
(since they may arrive out of order, or packets may get lost totally). This
|
|
|
|
|
can be disabled by setting the maximum demuxing delay to zero (via
|
|
|
|
|
the @code{max_delay} field of AVFormatContext).
|
2010-10-04 07:06:58 +00:00
|
|
|
|
|
2012-01-02 14:32:55 +00:00
|
|
|
|
When watching multi-bitrate Real-RTSP streams with @command{ffplay}, the
|
2010-10-04 07:06:58 +00:00
|
|
|
|
streams to display can be chosen with @code{-vst} @var{n} and
|
|
|
|
|
@code{-ast} @var{n} for video and audio respectively, and can be switched
|
|
|
|
|
on the fly by pressing @code{v} and @code{a}.
|
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
@subsection Examples
|
2010-10-04 07:06:58 +00:00
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
The following examples all make use of the @command{ffplay} and
|
|
|
|
|
@command{ffmpeg} tools.
|
2010-10-04 07:06:58 +00:00
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
@itemize
|
|
|
|
|
@item
|
|
|
|
|
Watch a stream over UDP, with a max reordering delay of 0.5 seconds:
|
2010-10-04 07:06:58 +00:00
|
|
|
|
@example
|
2011-10-17 23:33:09 +00:00
|
|
|
|
ffplay -max_delay 500000 -rtsp_transport udp rtsp://server/video.mp4
|
2010-10-04 07:06:58 +00:00
|
|
|
|
@end example
|
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
@item
|
|
|
|
|
Watch a stream tunneled over HTTP:
|
2010-10-04 07:06:58 +00:00
|
|
|
|
@example
|
2011-10-17 23:33:09 +00:00
|
|
|
|
ffplay -rtsp_transport http rtsp://server/video.mp4
|
2010-10-04 07:06:58 +00:00
|
|
|
|
@end example
|
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
@item
|
|
|
|
|
Send a stream in realtime to a RTSP server, for others to watch:
|
2010-10-04 07:06:58 +00:00
|
|
|
|
@example
|
|
|
|
|
ffmpeg -re -i @var{input} -f rtsp -muxdelay 0.1 rtsp://server/live.sdp
|
|
|
|
|
@end example
|
|
|
|
|
|
2013-12-29 15:43:48 +00:00
|
|
|
|
@item
|
|
|
|
|
Receive a stream in realtime:
|
2012-07-10 17:36:11 +00:00
|
|
|
|
@example
|
2012-07-13 15:17:21 +00:00
|
|
|
|
ffmpeg -rtsp_flags listen -i rtsp://ownaddress/live.sdp @var{output}
|
2012-07-10 17:36:11 +00:00
|
|
|
|
@end example
|
2013-12-29 15:43:48 +00:00
|
|
|
|
@end itemize
|
2013-04-07 01:39:56 +00:00
|
|
|
|
|
2010-10-09 18:50:02 +00:00
|
|
|
|
@section sap
|
|
|
|
|
|
|
|
|
|
Session Announcement Protocol (RFC 2974). This is not technically a
|
2010-10-13 09:06:59 +00:00
|
|
|
|
protocol handler in libavformat, it is a muxer and demuxer.
|
2010-10-09 18:50:02 +00:00
|
|
|
|
It is used for signalling of RTP streams, by announcing the SDP for the
|
|
|
|
|
streams regularly on a separate port.
|
|
|
|
|
|
2010-10-13 09:06:59 +00:00
|
|
|
|
@subsection Muxer
|
|
|
|
|
|
2010-10-09 18:50:02 +00:00
|
|
|
|
The syntax for a SAP url given to the muxer is:
|
|
|
|
|
@example
|
|
|
|
|
sap://@var{destination}[:@var{port}][?@var{options}]
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
The RTP packets are sent to @var{destination} on port @var{port},
|
|
|
|
|
or to port 5004 if no port is specified.
|
|
|
|
|
@var{options} is a @code{&}-separated list. The following options
|
|
|
|
|
are supported:
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
|
|
@item announce_addr=@var{address}
|
|
|
|
|
Specify the destination IP address for sending the announcements to.
|
|
|
|
|
If omitted, the announcements are sent to the commonly used SAP
|
|
|
|
|
announcement multicast address 224.2.127.254 (sap.mcast.net), or
|
|
|
|
|
ff0e::2:7ffe if @var{destination} is an IPv6 address.
|
|
|
|
|
|
|
|
|
|
@item announce_port=@var{port}
|
|
|
|
|
Specify the port to send the announcements on, defaults to
|
|
|
|
|
9875 if not specified.
|
|
|
|
|
|
|
|
|
|
@item ttl=@var{ttl}
|
|
|
|
|
Specify the time to live value for the announcements and RTP packets,
|
|
|
|
|
defaults to 255.
|
|
|
|
|
|
|
|
|
|
@item same_port=@var{0|1}
|
|
|
|
|
If set to 1, send all RTP streams on the same port pair. If zero (the
|
|
|
|
|
default), all streams are sent on unique ports, with each stream on a
|
|
|
|
|
port 2 numbers higher than the previous.
|
|
|
|
|
VLC/Live555 requires this to be set to 1, to be able to receive the stream.
|
2010-10-13 09:06:59 +00:00
|
|
|
|
The RTP stack in libavformat for receiving requires all streams to be sent
|
|
|
|
|
on unique ports.
|
2010-10-09 18:50:02 +00:00
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
Example command lines follow.
|
|
|
|
|
|
|
|
|
|
To broadcast a stream on the local subnet, for watching in VLC:
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
ffmpeg -re -i @var{input} -f sap sap://224.0.0.255?same_port=1
|
|
|
|
|
@end example
|
|
|
|
|
|
2012-01-02 14:32:55 +00:00
|
|
|
|
Similarly, for watching in @command{ffplay}:
|
2010-10-13 09:06:59 +00:00
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
ffmpeg -re -i @var{input} -f sap sap://224.0.0.255
|
|
|
|
|
@end example
|
|
|
|
|
|
2012-01-02 14:32:55 +00:00
|
|
|
|
And for watching in @command{ffplay}, over IPv6:
|
2010-10-13 09:06:59 +00:00
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
ffmpeg -re -i @var{input} -f sap sap://[ff0e::1:2:3:4]
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
@subsection Demuxer
|
|
|
|
|
|
|
|
|
|
The syntax for a SAP url given to the demuxer is:
|
|
|
|
|
@example
|
|
|
|
|
sap://[@var{address}][:@var{port}]
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
@var{address} is the multicast address to listen for announcements on,
|
|
|
|
|
if omitted, the default 224.2.127.254 (sap.mcast.net) is used. @var{port}
|
|
|
|
|
is the port that is listened on, 9875 if omitted.
|
|
|
|
|
|
|
|
|
|
The demuxers listens for announcements on the given address and port.
|
|
|
|
|
Once an announcement is received, it tries to receive that particular stream.
|
|
|
|
|
|
|
|
|
|
Example command lines follow.
|
|
|
|
|
|
|
|
|
|
To play back the first stream announced on the normal SAP multicast address:
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
ffplay sap://
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
To play back the first stream announced on one the default IPv6 SAP multicast address:
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
ffplay sap://[ff0e::2:7ffe]
|
|
|
|
|
@end example
|
|
|
|
|
|
2013-06-19 05:20:13 +00:00
|
|
|
|
@section sctp
|
|
|
|
|
|
|
|
|
|
Stream Control Transmission Protocol.
|
|
|
|
|
|
|
|
|
|
The accepted URL syntax is:
|
|
|
|
|
@example
|
|
|
|
|
sctp://@var{host}:@var{port}[?@var{options}]
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
The protocol accepts the following options:
|
|
|
|
|
@table @option
|
|
|
|
|
@item listen
|
|
|
|
|
If set to any value, listen for an incoming connection. Outgoing connection is done by default.
|
|
|
|
|
|
|
|
|
|
@item max_streams
|
|
|
|
|
Set the maximum number of streams. By default no limit is set.
|
|
|
|
|
@end table
|
|
|
|
|
|
2018-03-26 15:37:49 +00:00
|
|
|
|
@section srt
|
|
|
|
|
|
|
|
|
|
Haivision Secure Reliable Transport Protocol via libsrt.
|
|
|
|
|
|
|
|
|
|
The supported syntax for a SRT URL is:
|
|
|
|
|
@example
|
|
|
|
|
srt://@var{hostname}:@var{port}[?@var{options}]
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
@var{options} contains a list of &-separated options of the form
|
|
|
|
|
@var{key}=@var{val}.
|
|
|
|
|
|
|
|
|
|
or
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
@var{options} srt://@var{hostname}:@var{port}
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
@var{options} contains a list of '-@var{key} @var{val}'
|
|
|
|
|
options.
|
|
|
|
|
|
|
|
|
|
This protocol accepts the following options.
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item connect_timeout
|
|
|
|
|
Connection timeout; SRT cannot connect for RTT > 1500 msec
|
|
|
|
|
(2 handshake exchanges) with the default connect timeout of
|
|
|
|
|
3 seconds. This option applies to the caller and rendezvous
|
|
|
|
|
connection modes. The connect timeout is 10 times the value
|
|
|
|
|
set for the rendezvous mode (which can be used as a
|
|
|
|
|
workaround for this connection problem with earlier versions).
|
|
|
|
|
|
|
|
|
|
@item ffs=@var{bytes}
|
|
|
|
|
Flight Flag Size (Window Size), in bytes. FFS is actually an
|
|
|
|
|
internal parameter and you should set it to not less than
|
|
|
|
|
@option{recv_buffer_size} and @option{mss}. The default value
|
|
|
|
|
is relatively large, therefore unless you set a very large receiver buffer,
|
|
|
|
|
you do not need to change this option. Default value is 25600.
|
|
|
|
|
|
|
|
|
|
@item inputbw=@var{bytes/seconds}
|
|
|
|
|
Sender nominal input rate, in bytes per seconds. Used along with
|
|
|
|
|
@option{oheadbw}, when @option{maxbw} is set to relative (0), to
|
|
|
|
|
calculate maximum sending rate when recovery packets are sent
|
|
|
|
|
along with the main media stream:
|
|
|
|
|
@option{inputbw} * (100 + @option{oheadbw}) / 100
|
|
|
|
|
if @option{inputbw} is not set while @option{maxbw} is set to
|
|
|
|
|
relative (0), the actual input rate is evaluated inside
|
|
|
|
|
the library. Default value is 0.
|
|
|
|
|
|
|
|
|
|
@item iptos=@var{tos}
|
|
|
|
|
IP Type of Service. Applies to sender only. Default value is 0xB8.
|
|
|
|
|
|
|
|
|
|
@item ipttl=@var{ttl}
|
|
|
|
|
IP Time To Live. Applies to sender only. Default value is 64.
|
|
|
|
|
|
2018-05-21 07:40:17 +00:00
|
|
|
|
@item latency
|
|
|
|
|
Timestamp-based Packet Delivery Delay.
|
|
|
|
|
Used to absorb bursts of missed packet retransmissions.
|
|
|
|
|
This flag sets both @option{rcvlatency} and @option{peerlatency}
|
|
|
|
|
to the same value. Note that prior to version 1.3.0
|
|
|
|
|
this is the only flag to set the latency, however
|
|
|
|
|
this is effectively equivalent to setting @option{peerlatency},
|
|
|
|
|
when side is sender and @option{rcvlatency}
|
|
|
|
|
when side is receiver, and the bidirectional stream
|
|
|
|
|
sending is not supported.
|
|
|
|
|
|
2018-03-26 15:37:49 +00:00
|
|
|
|
@item listen_timeout
|
|
|
|
|
Set socket listen timeout.
|
|
|
|
|
|
|
|
|
|
@item maxbw=@var{bytes/seconds}
|
|
|
|
|
Maximum sending bandwidth, in bytes per seconds.
|
|
|
|
|
-1 infinite (CSRTCC limit is 30mbps)
|
|
|
|
|
0 relative to input rate (see @option{inputbw})
|
|
|
|
|
>0 absolute limit value
|
|
|
|
|
Default value is 0 (relative)
|
|
|
|
|
|
|
|
|
|
@item mode=@var{caller|listener|rendezvous}
|
|
|
|
|
Connection mode.
|
|
|
|
|
@option{caller} opens client connection.
|
|
|
|
|
@option{listener} starts server to listen for incoming connections.
|
|
|
|
|
@option{rendezvous} use Rendez-Vous connection mode.
|
|
|
|
|
Default value is caller.
|
|
|
|
|
|
|
|
|
|
@item mss=@var{bytes}
|
|
|
|
|
Maximum Segment Size, in bytes. Used for buffer allocation
|
|
|
|
|
and rate calculation using a packet counter assuming fully
|
|
|
|
|
filled packets. The smallest MSS between the peers is
|
|
|
|
|
used. This is 1500 by default in the overall internet.
|
|
|
|
|
This is the maximum size of the UDP packet and can be
|
|
|
|
|
only decreased, unless you have some unusual dedicated
|
|
|
|
|
network settings. Default value is 1500.
|
|
|
|
|
|
|
|
|
|
@item nakreport=@var{1|0}
|
|
|
|
|
If set to 1, Receiver will send `UMSG_LOSSREPORT` messages
|
|
|
|
|
periodically until a lost packet is retransmitted or
|
|
|
|
|
intentionally dropped. Default value is 1.
|
|
|
|
|
|
|
|
|
|
@item oheadbw=@var{percents}
|
|
|
|
|
Recovery bandwidth overhead above input rate, in percents.
|
|
|
|
|
See @option{inputbw}. Default value is 25%.
|
|
|
|
|
|
|
|
|
|
@item passphrase=@var{string}
|
|
|
|
|
HaiCrypt Encryption/Decryption Passphrase string, length
|
|
|
|
|
from 10 to 79 characters. The passphrase is the shared
|
|
|
|
|
secret between the sender and the receiver. It is used
|
|
|
|
|
to generate the Key Encrypting Key using PBKDF2
|
|
|
|
|
(Password-Based Key Derivation Function). It is used
|
|
|
|
|
only if @option{pbkeylen} is non-zero. It is used on
|
|
|
|
|
the receiver only if the received data is encrypted.
|
|
|
|
|
The configured passphrase cannot be recovered (write-only).
|
|
|
|
|
|
2019-12-01 13:09:13 +00:00
|
|
|
|
@item enforced_encryption=@var{1|0}
|
|
|
|
|
If true, both connection parties must have the same password
|
|
|
|
|
set (including empty, that is, with no encryption). If the
|
|
|
|
|
password doesn't match or only one side is unencrypted,
|
|
|
|
|
the connection is rejected. Default is true.
|
|
|
|
|
|
|
|
|
|
@item kmrefreshrate=@var{packets}
|
|
|
|
|
The number of packets to be transmitted after which the
|
|
|
|
|
encryption key is switched to a new key. Default is -1.
|
|
|
|
|
-1 means auto (0x1000000 in srt library). The range for
|
|
|
|
|
this option is integers in the 0 - @code{INT_MAX}.
|
|
|
|
|
|
|
|
|
|
@item kmpreannounce=@var{packets}
|
|
|
|
|
The interval between when a new encryption key is sent and
|
|
|
|
|
when switchover occurs. This value also applies to the
|
|
|
|
|
subsequent interval between when switchover occurs and
|
|
|
|
|
when the old encryption key is decommissioned. Default is -1.
|
|
|
|
|
-1 means auto (0x1000 in srt library). The range for
|
|
|
|
|
this option is integers in the 0 - @code{INT_MAX}.
|
|
|
|
|
|
2018-09-02 22:11:23 +00:00
|
|
|
|
@item payload_size=@var{bytes}
|
2018-05-21 06:55:25 +00:00
|
|
|
|
Sets the maximum declared size of a packet transferred
|
|
|
|
|
during the single call to the sending function in Live
|
|
|
|
|
mode. Use 0 if this value isn't used (which is default in
|
|
|
|
|
file mode).
|
2018-09-02 22:11:23 +00:00
|
|
|
|
Default is -1 (automatic), which typically means MPEG-TS;
|
|
|
|
|
if you are going to use SRT
|
2018-05-21 06:55:25 +00:00
|
|
|
|
to send any different kind of payload, such as, for example,
|
|
|
|
|
wrapping a live stream in very small frames, then you can
|
|
|
|
|
use a bigger maximum frame size, though not greater than
|
|
|
|
|
1456 bytes.
|
|
|
|
|
|
2018-09-02 22:11:23 +00:00
|
|
|
|
@item pkt_size=@var{bytes}
|
|
|
|
|
Alias for @samp{payload_size}.
|
|
|
|
|
|
2018-05-21 07:40:17 +00:00
|
|
|
|
@item peerlatency
|
|
|
|
|
The latency value (as described in @option{rcvlatency}) that is
|
|
|
|
|
set by the sender side as a minimum value for the receiver.
|
|
|
|
|
|
2018-03-26 15:37:49 +00:00
|
|
|
|
@item pbkeylen=@var{bytes}
|
|
|
|
|
Sender encryption key length, in bytes.
|
|
|
|
|
Only can be set to 0, 16, 24 and 32.
|
|
|
|
|
Enable sender encryption if not 0.
|
|
|
|
|
Not required on receiver (set to 0),
|
|
|
|
|
key size obtained from sender in HaiCrypt handshake.
|
|
|
|
|
Default value is 0.
|
|
|
|
|
|
2018-05-21 07:40:17 +00:00
|
|
|
|
@item rcvlatency
|
|
|
|
|
The time that should elapse since the moment when the
|
|
|
|
|
packet was sent and the moment when it's delivered to
|
|
|
|
|
the receiver application in the receiving function.
|
|
|
|
|
This time should be a buffer time large enough to cover
|
|
|
|
|
the time spent for sending, unexpectedly extended RTT
|
|
|
|
|
time, and the time needed to retransmit the lost UDP
|
|
|
|
|
packet. The effective latency value will be the maximum
|
|
|
|
|
of this options' value and the value of @option{peerlatency}
|
|
|
|
|
set by the peer side. Before version 1.3.0 this option
|
|
|
|
|
is only available as @option{latency}.
|
|
|
|
|
|
2018-03-26 15:37:49 +00:00
|
|
|
|
@item recv_buffer_size=@var{bytes}
|
2018-10-23 04:34:29 +00:00
|
|
|
|
Set UDP receive buffer size, expressed in bytes.
|
2018-03-26 15:37:49 +00:00
|
|
|
|
|
|
|
|
|
@item send_buffer_size=@var{bytes}
|
2018-10-23 04:34:29 +00:00
|
|
|
|
Set UDP send buffer size, expressed in bytes.
|
2018-03-26 15:37:49 +00:00
|
|
|
|
|
2020-02-13 22:50:32 +00:00
|
|
|
|
@item timeout
|
2020-02-15 10:29:28 +00:00
|
|
|
|
Set raise error timeouts for read, write and connect operations. Note that the
|
|
|
|
|
SRT library has internal timeouts which can be controlled separately, the
|
|
|
|
|
value set here is only a cap on those.
|
2018-03-26 15:37:49 +00:00
|
|
|
|
|
|
|
|
|
@item tlpktdrop=@var{1|0}
|
|
|
|
|
Too-late Packet Drop. When enabled on receiver, it skips
|
|
|
|
|
missing packets that have not been delivered in time and
|
|
|
|
|
delivers the following packets to the application when
|
|
|
|
|
their time-to-play has come. It also sends a fake ACK to
|
|
|
|
|
the sender. When enabled on sender and enabled on the
|
|
|
|
|
receiving peer, the sender drops the older packets that
|
|
|
|
|
have no chance of being delivered in time. It was
|
|
|
|
|
automatically enabled in the sender if the receiver
|
|
|
|
|
supports it.
|
|
|
|
|
|
2018-10-23 04:34:29 +00:00
|
|
|
|
@item sndbuf=@var{bytes}
|
|
|
|
|
Set send buffer size, expressed in bytes.
|
|
|
|
|
|
|
|
|
|
@item rcvbuf=@var{bytes}
|
|
|
|
|
Set receive buffer size, expressed in bytes.
|
|
|
|
|
|
|
|
|
|
Receive buffer must not be greater than @option{ffs}.
|
|
|
|
|
|
|
|
|
|
@item lossmaxttl=@var{packets}
|
|
|
|
|
The value up to which the Reorder Tolerance may grow. When
|
|
|
|
|
Reorder Tolerance is > 0, then packet loss report is delayed
|
|
|
|
|
until that number of packets come in. Reorder Tolerance
|
|
|
|
|
increases every time a "belated" packet has come, but it
|
|
|
|
|
wasn't due to retransmission (that is, when UDP packets tend
|
|
|
|
|
to come out of order), with the difference between the latest
|
|
|
|
|
sequence and this packet's sequence, and not more than the
|
|
|
|
|
value of this option. By default it's 0, which means that this
|
|
|
|
|
mechanism is turned off, and the loss report is always sent
|
|
|
|
|
immediately upon experiencing a "gap" in sequences.
|
|
|
|
|
|
|
|
|
|
@item minversion
|
|
|
|
|
The minimum SRT version that is required from the peer. A connection
|
|
|
|
|
to a peer that does not satisfy the minimum version requirement
|
|
|
|
|
will be rejected.
|
|
|
|
|
|
|
|
|
|
The version format in hex is 0xXXYYZZ for x.y.z in human readable
|
|
|
|
|
form.
|
|
|
|
|
|
|
|
|
|
@item streamid=@var{string}
|
|
|
|
|
A string limited to 512 characters that can be set on the socket prior
|
|
|
|
|
to connecting. This stream ID will be able to be retrieved by the
|
|
|
|
|
listener side from the socket that is returned from srt_accept and
|
|
|
|
|
was connected by a socket with that set stream ID. SRT does not enforce
|
|
|
|
|
any special interpretation of the contents of this string.
|
|
|
|
|
This option doesn’t make sense in Rendezvous connection; the result
|
|
|
|
|
might be that simply one side will override the value from the other
|
|
|
|
|
side and it’s the matter of luck which one would win
|
|
|
|
|
|
|
|
|
|
@item smoother=@var{live|file}
|
|
|
|
|
The type of Smoother used for the transmission for that socket, which
|
|
|
|
|
is responsible for the transmission and congestion control. The Smoother
|
|
|
|
|
type must be exactly the same on both connecting parties, otherwise
|
|
|
|
|
the connection is rejected.
|
|
|
|
|
|
|
|
|
|
@item messageapi=@var{1|0}
|
|
|
|
|
When set, this socket uses the Message API, otherwise it uses Buffer
|
|
|
|
|
API. Note that in live mode (see @option{transtype}) there’s only
|
|
|
|
|
message API available. In File mode you can chose to use one of two modes:
|
|
|
|
|
|
|
|
|
|
Stream API (default, when this option is false). In this mode you may
|
|
|
|
|
send as many data as you wish with one sending instruction, or even use
|
|
|
|
|
dedicated functions that read directly from a file. The internal facility
|
|
|
|
|
will take care of any speed and congestion control. When receiving, you
|
|
|
|
|
can also receive as many data as desired, the data not extracted will be
|
|
|
|
|
waiting for the next call. There is no boundary between data portions in
|
|
|
|
|
the Stream mode.
|
|
|
|
|
|
|
|
|
|
Message API. In this mode your single sending instruction passes exactly
|
|
|
|
|
one piece of data that has boundaries (a message). Contrary to Live mode,
|
|
|
|
|
this message may span across multiple UDP packets and the only size
|
|
|
|
|
limitation is that it shall fit as a whole in the sending buffer. The
|
|
|
|
|
receiver shall use as large buffer as necessary to receive the message,
|
|
|
|
|
otherwise the message will not be given up. When the message is not
|
|
|
|
|
complete (not all packets received or there was a packet loss) it will
|
|
|
|
|
not be given up.
|
|
|
|
|
|
|
|
|
|
@item transtype=@var{live|file}
|
|
|
|
|
Sets the transmission type for the socket, in particular, setting this
|
|
|
|
|
option sets multiple other parameters to their default values as required
|
|
|
|
|
for a particular transmission type.
|
|
|
|
|
|
|
|
|
|
live: Set options as for live transmission. In this mode, you should
|
|
|
|
|
send by one sending instruction only so many data that fit in one UDP packet,
|
|
|
|
|
and limited to the value defined first in @option{payload_size} (1316 is
|
|
|
|
|
default in this mode). There is no speed control in this mode, only the
|
|
|
|
|
bandwidth control, if configured, in order to not exceed the bandwidth with
|
|
|
|
|
the overhead transmission (retransmitted and control packets).
|
|
|
|
|
|
|
|
|
|
file: Set options as for non-live transmission. See @option{messageapi}
|
|
|
|
|
for further explanations
|
|
|
|
|
|
2019-12-01 06:03:37 +00:00
|
|
|
|
@item linger=@var{seconds}
|
|
|
|
|
The number of seconds that the socket waits for unsent data when closing.
|
|
|
|
|
Default is -1. -1 means auto (off with 0 seconds in live mode, on with 180
|
|
|
|
|
seconds in file mode). The range for this option is integers in the
|
|
|
|
|
0 - @code{INT_MAX}.
|
|
|
|
|
|
2018-03-26 15:37:49 +00:00
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
For more information see: @url{https://github.com/Haivision/srt}.
|
|
|
|
|
|
2013-06-19 05:21:00 +00:00
|
|
|
|
@section srtp
|
|
|
|
|
|
|
|
|
|
Secure Real-time Transport Protocol.
|
|
|
|
|
|
|
|
|
|
The accepted options are:
|
|
|
|
|
@table @option
|
|
|
|
|
@item srtp_in_suite
|
|
|
|
|
@item srtp_out_suite
|
|
|
|
|
Select input and output encoding suites.
|
|
|
|
|
|
|
|
|
|
Supported values:
|
|
|
|
|
@table @samp
|
|
|
|
|
@item AES_CM_128_HMAC_SHA1_80
|
|
|
|
|
@item SRTP_AES128_CM_HMAC_SHA1_80
|
|
|
|
|
@item AES_CM_128_HMAC_SHA1_32
|
|
|
|
|
@item SRTP_AES128_CM_HMAC_SHA1_32
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
@item srtp_in_params
|
|
|
|
|
@item srtp_out_params
|
|
|
|
|
Set input and output encoding parameters, which are expressed by a
|
|
|
|
|
base64-encoded representation of a binary block. The first 16 bytes of
|
|
|
|
|
this binary block are used as master key, the following 14 bytes are
|
|
|
|
|
used as master salt.
|
|
|
|
|
@end table
|
|
|
|
|
|
2014-02-25 20:50:54 +00:00
|
|
|
|
@section subfile
|
|
|
|
|
|
|
|
|
|
Virtually extract a segment of a file or another stream.
|
|
|
|
|
The underlying stream must be seekable.
|
|
|
|
|
|
|
|
|
|
Accepted options:
|
|
|
|
|
@table @option
|
|
|
|
|
@item start
|
|
|
|
|
Start offset of the extracted segment, in bytes.
|
|
|
|
|
@item end
|
|
|
|
|
End offset of the extracted segment, in bytes.
|
2017-11-15 12:06:19 +00:00
|
|
|
|
If set to 0, extract till end of file.
|
2014-02-25 20:50:54 +00:00
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
|
|
|
|
|
|
Extract a chapter from a DVD VOB file (start and end sectors obtained
|
|
|
|
|
externally and multiplied by 2048):
|
|
|
|
|
@example
|
|
|
|
|
subfile,,start,153391104,end,268142592,,:/media/dvd/VIDEO_TS/VTS_08_1.VOB
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
Play an AVI file directly from a TAR archive:
|
2015-03-11 10:22:04 +00:00
|
|
|
|
@example
|
2014-02-25 20:50:54 +00:00
|
|
|
|
subfile,,start,183241728,end,366490624,,:archive.tar
|
2015-03-11 10:22:04 +00:00
|
|
|
|
@end example
|
2014-02-25 20:50:54 +00:00
|
|
|
|
|
2017-11-15 12:06:19 +00:00
|
|
|
|
Play a MPEG-TS file from start offset till end:
|
|
|
|
|
@example
|
|
|
|
|
subfile,,start,32815239,end,0,,:video.ts
|
|
|
|
|
@end example
|
|
|
|
|
|
2016-07-18 12:42:22 +00:00
|
|
|
|
@section tee
|
|
|
|
|
|
2016-07-21 23:05:49 +00:00
|
|
|
|
Writes the output to multiple protocols. The individual outputs are separated
|
2016-07-18 12:42:22 +00:00
|
|
|
|
by |
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
tee:file://path/to/local/this.avi|file://path/to/local/that.avi
|
|
|
|
|
@end example
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@section tcp
|
|
|
|
|
|
2014-03-06 18:07:53 +00:00
|
|
|
|
Transmission Control Protocol.
|
2010-07-31 15:45:29 +00:00
|
|
|
|
|
2011-03-04 00:41:22 +00:00
|
|
|
|
The required syntax for a TCP url is:
|
|
|
|
|
@example
|
|
|
|
|
tcp://@var{hostname}:@var{port}[?@var{options}]
|
|
|
|
|
@end example
|
|
|
|
|
|
2013-12-24 15:27:34 +00:00
|
|
|
|
@var{options} contains a list of &-separated options of the form
|
|
|
|
|
@var{key}=@var{val}.
|
2011-03-04 00:41:22 +00:00
|
|
|
|
|
2013-12-24 15:27:34 +00:00
|
|
|
|
The list of supported options follows.
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item listen=@var{1|0}
|
|
|
|
|
Listen for an incoming connection. Default value is 0.
|
2011-03-04 00:41:22 +00:00
|
|
|
|
|
2012-09-13 00:43:29 +00:00
|
|
|
|
@item timeout=@var{microseconds}
|
2013-12-24 15:27:34 +00:00
|
|
|
|
Set raise error timeout, expressed in microseconds.
|
2012-09-13 00:43:29 +00:00
|
|
|
|
|
2013-12-24 15:27:34 +00:00
|
|
|
|
This option is only relevant in read mode: if no data arrived in more
|
|
|
|
|
than this time interval, raise error.
|
|
|
|
|
|
2015-03-05 11:05:17 +00:00
|
|
|
|
@item listen_timeout=@var{milliseconds}
|
|
|
|
|
Set listen timeout, expressed in milliseconds.
|
2016-01-19 18:22:13 +00:00
|
|
|
|
|
|
|
|
|
@item recv_buffer_size=@var{bytes}
|
|
|
|
|
Set receive buffer size, expressed bytes.
|
|
|
|
|
|
|
|
|
|
@item send_buffer_size=@var{bytes}
|
|
|
|
|
Set send buffer size, expressed bytes.
|
2017-11-13 20:20:18 +00:00
|
|
|
|
|
|
|
|
|
@item tcp_nodelay=@var{1|0}
|
|
|
|
|
Set TCP_NODELAY to disable Nagle's algorithm. Default value is 0.
|
2018-05-06 15:02:42 +00:00
|
|
|
|
|
|
|
|
|
@item tcp_mss=@var{bytes}
|
|
|
|
|
Set maximum segment size for outgoing TCP packets, expressed in bytes.
|
2013-12-24 15:27:34 +00:00
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
The following example shows how to setup a listening TCP connection
|
|
|
|
|
with @command{ffmpeg}, which is then accessed with @command{ffplay}:
|
2011-03-04 00:41:22 +00:00
|
|
|
|
@example
|
|
|
|
|
ffmpeg -i @var{input} -f @var{format} tcp://@var{hostname}:@var{port}?listen
|
|
|
|
|
ffplay tcp://@var{hostname}:@var{port}
|
|
|
|
|
@end example
|
|
|
|
|
|
2012-07-22 04:25:42 +00:00
|
|
|
|
@section tls
|
|
|
|
|
|
2011-02-22 10:02:01 +00:00
|
|
|
|
Transport Layer Security (TLS) / Secure Sockets Layer (SSL)
|
2012-07-22 04:25:42 +00:00
|
|
|
|
|
|
|
|
|
The required syntax for a TLS/SSL url is:
|
|
|
|
|
@example
|
|
|
|
|
tls://@var{hostname}:@var{port}[?@var{options}]
|
|
|
|
|
@end example
|
|
|
|
|
|
2011-02-22 10:02:01 +00:00
|
|
|
|
The following parameters can be set via command line options
|
|
|
|
|
(or in code via @code{AVOption}s):
|
|
|
|
|
|
2012-07-22 04:25:42 +00:00
|
|
|
|
@table @option
|
|
|
|
|
|
2013-09-27 07:22:42 +00:00
|
|
|
|
@item ca_file, cafile=@var{filename}
|
2011-02-22 10:02:01 +00:00
|
|
|
|
A file containing certificate authority (CA) root certificates to treat
|
|
|
|
|
as trusted. If the linked TLS library contains a default this might not
|
|
|
|
|
need to be specified for verification to work, but not all libraries and
|
|
|
|
|
setups have defaults built in.
|
2013-09-27 07:22:42 +00:00
|
|
|
|
The file must be in OpenSSL PEM format.
|
2011-02-22 10:02:01 +00:00
|
|
|
|
|
|
|
|
|
@item tls_verify=@var{1|0}
|
|
|
|
|
If enabled, try to verify the peer that we are communicating with.
|
|
|
|
|
Note, if using OpenSSL, this currently only makes sure that the
|
|
|
|
|
peer certificate is signed by one of the root certificates in the CA
|
|
|
|
|
database, but it does not validate that the certificate actually
|
2017-11-04 14:45:16 +00:00
|
|
|
|
matches the host name we are trying to connect to. (With other backends,
|
2011-02-22 10:02:01 +00:00
|
|
|
|
the host name is validated as well.)
|
|
|
|
|
|
|
|
|
|
This is disabled by default since it requires a CA database to be
|
|
|
|
|
provided by the caller in many cases.
|
|
|
|
|
|
2013-09-27 09:21:42 +00:00
|
|
|
|
@item cert_file, cert=@var{filename}
|
2013-09-19 09:30:52 +00:00
|
|
|
|
A file containing a certificate to use in the handshake with the peer.
|
|
|
|
|
(When operating as server, in listen mode, this is more often required
|
|
|
|
|
by the peer, while client certificates only are mandated in certain
|
|
|
|
|
setups.)
|
|
|
|
|
|
2013-09-27 09:21:42 +00:00
|
|
|
|
@item key_file, key=@var{filename}
|
2013-09-19 09:30:52 +00:00
|
|
|
|
A file containing the private key for the certificate.
|
|
|
|
|
|
|
|
|
|
@item listen=@var{1|0}
|
|
|
|
|
If enabled, listen for connections on the provided port, and assume
|
|
|
|
|
the server role in the handshake instead of the client role.
|
2012-07-22 04:25:42 +00:00
|
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
Example command lines:
|
|
|
|
|
|
|
|
|
|
To create a TLS/SSL server that serves an input stream.
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
ffmpeg -i @var{input} -f @var{format} tls://@var{hostname}:@var{port}?listen&cert=@var{server.crt}&key=@var{server.key}
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
To play back a stream from the TLS/SSL server using @command{ffplay}:
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
ffplay tls://@var{hostname}:@var{port}
|
|
|
|
|
@end example
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@section udp
|
|
|
|
|
|
|
|
|
|
User Datagram Protocol.
|
|
|
|
|
|
2013-12-24 13:38:48 +00:00
|
|
|
|
The required syntax for an UDP URL is:
|
2010-09-25 10:16:15 +00:00
|
|
|
|
@example
|
|
|
|
|
udp://@var{hostname}:@var{port}[?@var{options}]
|
|
|
|
|
@end example
|
|
|
|
|
|
2012-07-18 14:13:51 +00:00
|
|
|
|
@var{options} contains a list of &-separated options of the form @var{key}=@var{val}.
|
|
|
|
|
|
2012-07-18 14:56:11 +00:00
|
|
|
|
In case threading is enabled on the system, a circular buffer is used
|
2014-03-06 18:07:53 +00:00
|
|
|
|
to store the incoming data, which allows one to reduce loss of data due to
|
2012-07-18 14:56:11 +00:00
|
|
|
|
UDP socket buffer overruns. The @var{fifo_size} and
|
|
|
|
|
@var{overrun_nonfatal} options are related to this buffer.
|
|
|
|
|
|
2012-07-18 14:13:51 +00:00
|
|
|
|
The list of supported options follows.
|
2010-09-25 10:16:15 +00:00
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item buffer_size=@var{size}
|
2014-03-21 23:53:19 +00:00
|
|
|
|
Set the UDP maximum socket buffer size in bytes. This is used to set either
|
|
|
|
|
the receive or send buffer size, depending on what the socket is used for.
|
2020-01-14 18:18:01 +00:00
|
|
|
|
Default is 32 KB for output, 384 KB for input. See also @var{fifo_size}.
|
2010-09-25 10:16:15 +00:00
|
|
|
|
|
2016-06-10 00:32:21 +00:00
|
|
|
|
@item bitrate=@var{bitrate}
|
|
|
|
|
If set to nonzero, the output will have the specified constant bitrate if the
|
|
|
|
|
input has enough packets to sustain it.
|
|
|
|
|
|
|
|
|
|
@item burst_bits=@var{bits}
|
|
|
|
|
When using @var{bitrate} this specifies the maximum number of bits in
|
|
|
|
|
packet bursts.
|
2016-03-08 20:27:45 +00:00
|
|
|
|
|
2010-09-25 10:16:15 +00:00
|
|
|
|
@item localport=@var{port}
|
2012-07-18 14:13:51 +00:00
|
|
|
|
Override the local UDP port to bind with.
|
2010-09-25 10:16:15 +00:00
|
|
|
|
|
2011-11-09 09:45:01 +00:00
|
|
|
|
@item localaddr=@var{addr}
|
2018-09-21 22:19:17 +00:00
|
|
|
|
Local IP address of a network interface used for sending packets or joining
|
|
|
|
|
multicast groups.
|
2011-11-09 09:45:01 +00:00
|
|
|
|
|
2010-09-25 10:16:15 +00:00
|
|
|
|
@item pkt_size=@var{size}
|
2012-07-18 14:13:51 +00:00
|
|
|
|
Set the size in bytes of UDP packets.
|
2010-09-25 10:16:15 +00:00
|
|
|
|
|
|
|
|
|
@item reuse=@var{1|0}
|
2012-07-18 14:13:51 +00:00
|
|
|
|
Explicitly allow or disallow reusing UDP sockets.
|
2010-09-25 10:16:15 +00:00
|
|
|
|
|
|
|
|
|
@item ttl=@var{ttl}
|
2012-07-18 14:13:51 +00:00
|
|
|
|
Set the time to live value (for multicast only).
|
2010-10-08 08:49:56 +00:00
|
|
|
|
|
|
|
|
|
@item connect=@var{1|0}
|
|
|
|
|
Initialize the UDP socket with @code{connect()}. In this case, the
|
2011-03-08 09:35:52 +00:00
|
|
|
|
destination address can't be changed with ff_udp_set_remote_url later.
|
2011-01-06 15:16:50 +00:00
|
|
|
|
If the destination address isn't known at the start, this option can
|
2011-03-08 09:35:52 +00:00
|
|
|
|
be specified in ff_udp_set_remote_url, too.
|
2010-10-08 08:49:56 +00:00
|
|
|
|
This allows finding out the source address for the packets with getsockname,
|
|
|
|
|
and makes writes return with AVERROR(ECONNREFUSED) if "destination
|
|
|
|
|
unreachable" is received.
|
2011-01-06 15:16:50 +00:00
|
|
|
|
For receiving, this gives the benefit of only receiving packets from
|
|
|
|
|
the specified peer address/port.
|
2012-06-21 11:19:56 +00:00
|
|
|
|
|
|
|
|
|
@item sources=@var{address}[,@var{address}]
|
2018-09-19 23:23:58 +00:00
|
|
|
|
Only receive packets sent from the specified addresses. In case of multicast,
|
|
|
|
|
also subscribe to multicast traffic coming from these addresses only.
|
2012-06-21 11:19:56 +00:00
|
|
|
|
|
|
|
|
|
@item block=@var{address}[,@var{address}]
|
2018-09-19 23:23:58 +00:00
|
|
|
|
Ignore packets sent from the specified addresses. In case of multicast, also
|
|
|
|
|
exclude the source addresses in the multicast subscription.
|
2012-07-15 18:56:08 +00:00
|
|
|
|
|
|
|
|
|
@item fifo_size=@var{units}
|
|
|
|
|
Set the UDP receiving circular buffer size, expressed as a number of
|
|
|
|
|
packets with size of 188 bytes. If not specified defaults to 7*4096.
|
|
|
|
|
|
|
|
|
|
@item overrun_nonfatal=@var{1|0}
|
|
|
|
|
Survive in case of UDP receiving circular buffer overrun. Default
|
|
|
|
|
value is 0.
|
2012-08-27 13:31:09 +00:00
|
|
|
|
|
|
|
|
|
@item timeout=@var{microseconds}
|
2013-12-24 13:38:48 +00:00
|
|
|
|
Set raise error timeout, expressed in microseconds.
|
|
|
|
|
|
|
|
|
|
This option is only relevant in read mode: if no data arrived in more
|
|
|
|
|
than this time interval, raise error.
|
2014-05-15 06:22:11 +00:00
|
|
|
|
|
|
|
|
|
@item broadcast=@var{1|0}
|
|
|
|
|
Explicitly allow or disallow UDP broadcasting.
|
|
|
|
|
|
|
|
|
|
Note that broadcasting may not work properly on networks having
|
|
|
|
|
a broadcast storm protection.
|
2010-09-25 10:16:15 +00:00
|
|
|
|
@end table
|
|
|
|
|
|
2013-12-27 11:43:35 +00:00
|
|
|
|
@subsection Examples
|
2010-09-25 10:16:15 +00:00
|
|
|
|
|
2013-12-24 13:38:48 +00:00
|
|
|
|
@itemize
|
|
|
|
|
@item
|
|
|
|
|
Use @command{ffmpeg} to stream over UDP to a remote endpoint:
|
2010-09-25 10:16:15 +00:00
|
|
|
|
@example
|
|
|
|
|
ffmpeg -i @var{input} -f @var{format} udp://@var{hostname}:@var{port}
|
|
|
|
|
@end example
|
|
|
|
|
|
2013-12-24 13:38:48 +00:00
|
|
|
|
@item
|
|
|
|
|
Use @command{ffmpeg} to stream in mpegts format over UDP using 188
|
|
|
|
|
sized UDP packets, using a large input buffer:
|
2010-09-25 10:16:15 +00:00
|
|
|
|
@example
|
|
|
|
|
ffmpeg -i @var{input} -f mpegts udp://@var{hostname}:@var{port}?pkt_size=188&buffer_size=65535
|
|
|
|
|
@end example
|
|
|
|
|
|
2013-12-24 13:38:48 +00:00
|
|
|
|
@item
|
|
|
|
|
Use @command{ffmpeg} to receive over UDP from a remote endpoint:
|
2010-09-25 10:16:15 +00:00
|
|
|
|
@example
|
2013-12-24 13:38:48 +00:00
|
|
|
|
ffmpeg -i udp://[@var{multicast-address}]:@var{port} ...
|
2010-09-25 10:16:15 +00:00
|
|
|
|
@end example
|
2013-12-24 13:38:48 +00:00
|
|
|
|
@end itemize
|
2010-09-25 10:16:15 +00:00
|
|
|
|
|
2013-07-29 23:34:56 +00:00
|
|
|
|
@section unix
|
|
|
|
|
|
|
|
|
|
Unix local socket
|
|
|
|
|
|
|
|
|
|
The required syntax for a Unix socket URL is:
|
|
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
unix://@var{filepath}
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
The following parameters can be set via command line options
|
|
|
|
|
(or in code via @code{AVOption}s):
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
@item timeout
|
|
|
|
|
Timeout in ms.
|
|
|
|
|
@item listen
|
|
|
|
|
Create the Unix socket in listening mode.
|
|
|
|
|
@end table
|
|
|
|
|
|
2019-07-30 18:39:32 +00:00
|
|
|
|
@section zmq
|
|
|
|
|
|
|
|
|
|
ZeroMQ asynchronous messaging using the libzmq library.
|
|
|
|
|
|
|
|
|
|
This library supports unicast streaming to multiple clients without relying on
|
|
|
|
|
an external server.
|
|
|
|
|
|
|
|
|
|
The required syntax for streaming or connecting to a stream is:
|
|
|
|
|
@example
|
|
|
|
|
zmq:tcp://ip-address:port
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
Create a localhost stream on port 5555:
|
|
|
|
|
@example
|
|
|
|
|
ffmpeg -re -i input -f mpegts zmq:tcp://127.0.0.1:5555
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
Multiple clients may connect to the stream using:
|
|
|
|
|
@example
|
|
|
|
|
ffplay zmq:tcp://127.0.0.1:5555
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
Streaming to multiple clients is implemented using a ZeroMQ Pub-Sub pattern.
|
|
|
|
|
The server side binds to a port and publishes data. Clients connect to the
|
|
|
|
|
server (via IP address/port) and subscribe to the stream. The order in which
|
|
|
|
|
the server and client start generally does not matter.
|
|
|
|
|
|
|
|
|
|
ffmpeg must be compiled with the --enable-libzmq option to support
|
|
|
|
|
this protocol.
|
|
|
|
|
|
|
|
|
|
Options can be set on the @command{ffmpeg}/@command{ffplay} command
|
|
|
|
|
line. The following options are supported:
|
|
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
|
|
@item pkt_size
|
|
|
|
|
Forces the maximum packet size for sending/receiving data. The default value is
|
|
|
|
|
32,768 bytes. On the server side, this sets the maximum size of sent packets
|
|
|
|
|
via ZeroMQ. On the clients, it sets an internal buffer size for receiving
|
|
|
|
|
packets. Note that pkt_size on the clients should be equal to or greater than
|
|
|
|
|
pkt_size on the server. Otherwise the received message may be truncated causing
|
|
|
|
|
decoding errors.
|
|
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
|
2010-07-31 15:45:29 +00:00
|
|
|
|
@c man end PROTOCOLS
|