On 11/28/18 4:41 PM, Andrey Semashev wrote: > The global_sidx flag causes errors like the following in movenc when media > segment removal is enabled via windos_size or remove_at_exit: > > Non-consecutive fragments, writing incorrect sidx > Unable to re-open output file for the second pass (faststart) Removing global_sidx flag adds sidx atom to each moof fragment adding significant bitrate overhead. Instead I have submitted a patch to handle this case cleanly in movenc. http://ffmpeg.org/pipermail/ffmpeg-devel/2018-November/236873.html Please try the above patch and let me know if that will work for you. > --- > libavformat/dashenc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c > index 6ce70e0076..cb49641b4e 100644 > --- a/libavformat/dashenc.c > +++ b/libavformat/dashenc.c > @@ -1141,7 +1141,7 @@ static int dash_init(AVFormatContext *s) > > if (os->segment_type == SEGMENT_TYPE_MP4) { > if (c->streaming) > - av_dict_set(&opts, "movflags", > "frag_every_frame+dash+delay_moov+global_sidx", 0); > + av_dict_set(&opts, "movflags", > "frag_every_frame+dash+delay_moov", 0); > else > av_dict_set(&opts, "movflags", > "frag_custom+dash+delay_moov", 0); > } else {
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel