From: "\"zhilizhao(赵志立)\"" <quinkblack@foxmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avformat/mov: discard data streams with all zero sample_delta Date: Tue, 5 Jul 2022 21:35:32 +0800 Message-ID: <tencent_6F407F9A2C9F55AB3D4E4670B52DCA9A4E08@qq.com> (raw) In-Reply-To: <3c3b2623-ee21-6028-3f45-5c15d0ff22ec@gyani.pro> > On Jul 5, 2022, at 8:07 PM, Gyan Doshi <ffmpeg@gyani.pro> wrote: > > > > On 2022-07-05 01:20 pm, Zhao Zhili wrote: >> From: Zhao Zhili <zhilizhao@tencent.com> >> >> Streams with all zero sample_delta in 'stts' have all zero dts. >> They have higher chance be chose by mov_find_next_sample(), which >> leads to seek again and again. >> >> For example, GoPro created a 'GoPro SOS' stream: >> Stream #0:4[0x5](eng): Data: none (fdsc / 0x63736466), 13 kb/s (default) >> Metadata: >> creation_time : 2022-06-21T08:49:19.000000Z >> handler_name : GoPro SOS >> >> With 'ffprobe -show_frames http://example.com/gopro.mp4', ffprobe >> blocks until all samples in 'GoPro SOS' stream are consumed first. >> >> Signed-off-by: Zhao Zhili <zhilizhao@tencent.com> >> --- >> libavformat/mov.c | 14 ++++++++++++++ >> 1 file changed, 14 insertions(+) >> >> diff --git a/libavformat/mov.c b/libavformat/mov.c >> index 88669faa70..2a4eb79f27 100644 >> --- a/libavformat/mov.c >> +++ b/libavformat/mov.c >> @@ -3062,6 +3062,20 @@ static int mov_read_stts(MOVContext *c, AVIOContext *pb, MOVAtom atom) >> st->nb_frames= total_sample_count; >> if (duration) >> st->duration= FFMIN(st->duration, duration); >> + >> + // All samples have zero duration. They have higher chance be chose by >> + // mov_find_next_sample, which leads to seek again and again. >> + // >> + // It's AVERROR_INVALIDDATA actually, but such files exist in the wild. >> + // So only mark data stream as discarded for safety. >> + if (!duration && sc->stts_count && >> + st->codecpar->codec_type == AVMEDIA_TYPE_DATA) { >> + av_log(c->fc, AV_LOG_WARNING, >> + "All samples in data stream index:id [%d:%d] have zero duration, " >> + "discard the stream\n", >> + st->index, st->id); >> + st->discard = AVDISCARD_ALL; >> + } >> sc->track_end = duration; >> return 0; >> } > > So this will allow audio and video streams to be demuxed, but not data? That distinction seems arbitrary. Disable audio/video streams may create regression. It’s unlikely for random and broken data stream. > > Print a warning and assign a duration to each sample. Either 1 or if not zero/Inf, st->duration/st->nb_frames. Set sample_duration to 1 doesn’t work. Dts still far behind other streams. Set sample_duration st->duration/st->nb_frames works for me, but I prefer current strategy for the following reasons: 1. AVDISCARD_ALL is more close to AVERROR_INVALIDDATA by giving up instead of trying correction and hope it works, which may not, e.g., st->duration is broken, or bad interleave even though we fixed sample_duration. 2. libavformat users can enable the stream and get the original dts/duration, if they want to. > > Regards, > Gyan > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-07-05 13:37 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-05 7:50 Zhao Zhili 2022-07-05 12:07 ` Gyan Doshi 2022-07-05 13:35 ` "zhilizhao(赵志立)" [this message] 2022-07-05 14:33 ` Gyan Doshi 2022-07-06 2:53 ` "zhilizhao(赵志立)" 2022-07-06 4:09 ` Gyan Doshi 2022-07-06 5:24 ` "zhilizhao(赵志立)" 2022-07-06 5:58 ` Gyan Doshi 2022-07-06 6:59 ` [FFmpeg-devel] [PATCH v2] " Zhao Zhili 2022-07-06 7:05 ` [FFmpeg-devel] [PATCH v3] " Zhao Zhili 2022-07-14 11:33 ` "zhilizhao(赵志立)"
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=tencent_6F407F9A2C9F55AB3D4E4670B52DCA9A4E08@qq.com \ --to=quinkblack@foxmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git