On Mon, 24 Nov 2014, Luca Barbato wrote:
On 24/11/14 12:12, Bryan Huh wrote:
+ { "init_seg_name", "DASH-templated name to used for the initialization
segment", OFFSET(init_seg_name), AV_OPT_TYPE_STRING, {.str =
"init-stream$RepresentationID$.m4s"}, 0, 0, E },
+ { "media_seg_name", "DASH-templated name to used for the media
segments", OFFSET(media_seg_name), AV_OPT_TYPE_STRING, {.str =
"chunk-stream$RepresentationID$-$Number%05d$.m4s"}, 0, 0, E },
+ { "single_file_name", "DASH-templated name to be used for baseURL.
Implies storing all segments in one file, accessed using byte ranges",
OFFSET(single_file_name), AV_OPT_TYPE_STRING, { .str = NULL }, 0, 0, E },
{ NULL },
Is the $name$ syntax common for DASH? otherwise using the common %s and %d
might be less surprising for the people already using the image and segmenter
muxers.
Yes, it's part of the spec. The point is that you can write a segment name
template like this, so you don't need to write the full filename for every
segment file in the list.
// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
