This delays writing the moov until the first fragment is written,
or can be flushed by the caller explicitly when wanted. If the first
sample in all streams is available at this point, we can write
a proper editlist at this point, allowing streams to start at
something else than dts=0. For AC3 and DNXHD, a packet is
needed in order to write the moov header properly.
This isn't added to the normal behaviour for empty_moov, since
the behaviour that ftyp+moov is written during avformat_write_header
would be changed. Callers that split the output stream into header+segments
(either by flushing manually, with the custom_frag flag set, or by
just differentiating between data written during avformat_write_header
and the rest) will need to be adjusted to take this option into use.
For handling streams that start at something else than dts=0, an
alternative would be to use different kinds of heuristics for
guessing the start dts (using AVCodecContext delay or has_b_frames
together with the frame rate), but this is not reliable and doesn't
necessarily work well with stream copy, and wouldn't work for getting
the right initialization data for AC3 or DNXHD either.
Signed-off-by: Martin Storsjö <martin@martin.st>
{"default_base_moof","Set the default-base-is-moof flag in tfhd atoms",0,AV_OPT_TYPE_CONST,{.i64=FF_MOV_FLAG_DEFAULT_BASE_MOOF},INT_MIN,INT_MAX,AV_OPT_FLAG_ENCODING_PARAM,"movflags"},
{"frag_discont","Signal that the next fragment is discontinuous from earlier ones",0,AV_OPT_TYPE_CONST,{.i64=FF_MOV_FLAG_FRAG_DISCONT},INT_MIN,INT_MAX,AV_OPT_FLAG_ENCODING_PARAM,"movflags"},
{"delay_moov","Delay writing the initial moov until the first fragment is cut, or until the first fragment flush",0,AV_OPT_TYPE_CONST,{.i64=FF_MOV_FLAG_DELAY_MOOV},INT_MIN,INT_MAX,AV_OPT_FLAG_ENCODING_PARAM,"movflags"},