From cf589faa5b7aed3bb38e08dcd00bd951e69686d1 Mon Sep 17 00:00:00 2001 From: Martin Storsjö Date: Wed, 29 Oct 2014 11:53:21 +0200 Subject: movenc: Add a flag for using default-base-is-moof in tfhd atoms MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Similarly to the omit_tfhd_offset flag added in e7bf085b, this avoids writing absolute byte positions to the file, making them more easily streamable. This is a new feature from 14496-12:2012, so application support isn't necessarily too widespread yet (support for it in libav was added in 20f95f21f in July 2014). Signed-off-by: Martin Storsjö --- doc/muxers.texi | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'doc/muxers.texi') diff --git a/doc/muxers.texi b/doc/muxers.texi index 7c7e27c3a4..6d2c49562b 100644 --- a/doc/muxers.texi +++ b/doc/muxers.texi @@ -340,6 +340,13 @@ cause failures when the file is reprocessed with certain tagging programs. @item -movflags omit_tfhd_offset Do not write any absolute base_data_offset in tfhd atoms. This avoids tying fragments to absolute byte positions in the file/streams. +@item -movflags default_base_moof +Similarly to the omit_tfhd_offset, this flag avoids writing the +absolute base_data_offset field in tfhd atoms, but does so by using +the new default-base-is-moof flag instead. This flag is new from +14496-12:2012. This may make the fragments easier to parse in certain +circumstances (avoiding basing track fragment location calculations +on the implicit end of the previous track fragment). @end table Smooth Streaming content can be pushed in real time to a publishing -- cgit v1.2.3