On 11/29/18 8:28 PM, Andrey Semashev wrote: > On 11/28/18 7:25 PM, Jeyapal, Karthick wrote: >> >> 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. > > Yes, that patch seems to fix the errors. Thanks. Hi Andrey,
That patch was not pushed due to some objections. I have submitted a new patch set addressing it. http://ffmpeg.org/pipermail/ffmpeg-devel/2018-December/237121.html Could you please try the above patchset and confirm if everything works as expected? Regards, Karthick > > On a slightly unrelated note, during testing, I've also seen different errors > like these: > > [AVFormatContext] Application provided duration: -1 / timestamp: 243456 is > out of range for mov/mp4 format > [AVFormatContext] pts has no value > > These happen when media segments are rotated and file deletion is enabled. > They don't seem to happen on every file rotation, though, and I can't find > what could be causing them. These errors are present regardless of the > global_sidx flag or your movenc patch. Do you have an idea what could be > causing them? > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
