On Fri, 27 Jan 2017, Peter Große wrote:

Signed-off-by: Peter Große <[email protected]>
---
doc/muxers.texi | 53 +++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 53 insertions(+)

diff --git a/doc/muxers.texi b/doc/muxers.texi
index 5430da7..95d8051 100644
--- a/doc/muxers.texi
+++ b/doc/muxers.texi
@@ -53,6 +53,59 @@ avconv -i INPUT -c:a pcm_u8 -c:v mpeg2video -f crc -

See also the @ref{framecrc} muxer.

+@anchor{dash}
+@section dash
+
+Dynamic Adaptive Streaming over HTTP (DASH) muxer that creates segments
+and manifest files according to the MPEG-DASH standard ISO/IEC 23009-1:2014.
+
+For more information see:
+
+@itemize @bullet
+@item
+WebM DASH Specification: 
@url{https://sites.google.com/a/webmproject.org/wiki/adaptive-streaming/webm-dash-specification}
+@item
+ISO DASH Specification: 
@url{http://standards.iso.org/ittf/PubliclyAvailableStandards/c065274_ISO_IEC_23009-1_2014.zip}
+@end itemize

I'd rather have the actual ISO spec first :P

+
+It creates a MPD manifest file and segment files for each stream.
+
+The segment filename might contain pre-defined identifiers used with 
SegmentTemplate
+as defined in section 5.3.9.4.4 of the standard. Available identifiers are 
"$RepresentationID$",
+"$Number$", "$Bandwidth$" and "$Time$".
+
+@example
+avconv -i in.nut -f dash
+@end example

It might be of value to show a full testcase also, where you use multiple quality streams for both audio and video.

I've used a command line like this locally for testing that:

./avconv -re -i <input> -map 0 -map 0 -acodec libfdk_aac -vcodec libx264 -b:v:0 800k -b:v:1 300k -s:v:1 320x170 -profile:v:1 baseline -profile:v:0 main -bf 1 -keyint_min 120 -g 120 -sc_threshold 0 -b_strategy 0 -use_timeline 1 -use_template 1 -window_size 5 -f dash -ar:a:1 22050 /path/to/out.mpd

This should afaik produce well-aligned keyframes in all substreams. Feel free to pick through this and see what of it makes sense to include in an example.

// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to