[extractor/common] Document forgotten fragment base and path interfaces

This commit is contained in:
Sergey M․ 2017-01-29 05:56:43 +07:00
parent d04621daf4
commit c58c2d63cb
No known key found for this signature in database
GPG Key ID: 2C393E0F18A9236D

View File

@ -121,9 +121,19 @@ class InfoExtractor(object):
download, lower-case. download, lower-case.
"http", "https", "rtsp", "rtmp", "rtmpe", "http", "https", "rtsp", "rtmp", "rtmpe",
"m3u8", "m3u8_native" or "http_dash_segments". "m3u8", "m3u8_native" or "http_dash_segments".
* fragments A list of fragments of the fragmented media, * fragment_base_url
with the following entries: Base URL for fragments. Each fragment's path
* "url" (mandatory) - fragment's URL value (if present) will be relative to
this URL.
* fragments A list of fragments of a fragmented media.
Each fragment entry must contain either an url
or a path. If an url is present it should be
considered by a client. Otherwise both path and
fragment_base_url must be present. Here is
the list of all potential fields:
* "url" - fragment's URL
* "path" - fragment's path relative to
fragment_base_url
* "duration" (optional, int or float) * "duration" (optional, int or float)
* "filesize" (optional, int) * "filesize" (optional, int)
* preference Order number of this format. If this field is * preference Order number of this format. If this field is