From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org> To: Steven Liu <lingjiujianke@gmail.com>, FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avformat/hls: Revert "reduce default max reload to 3" Date: Fri, 7 Feb 2025 02:39:56 +0000 Message-ID: <DM8P223MB03650CD0C95361B41E3CEC92BAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <CADxeRwkTu3pyGsXFz5CkA4zWX0n+F352rzPVyvTq_M=y6rtS=g@mail.gmail.com> > -----Original Message----- > From: Steven Liu <lingjiujianke@gmail.com> > Sent: Friday, February 7, 2025 3:24 AM > To: FFmpeg development discussions and patches <ffmpeg- > devel@ffmpeg.org> > Cc: softworkz <softworkz@hotmail.com> > Subject: Re: [FFmpeg-devel] [PATCH] avformat/hls: Revert "reduce > default max reload to 3" > > softworkz <ffmpegagent@gmail.com> 于2025年1月19日周日 16:52写道: > > > > From: softworkz <softworkz@hotmail.com> > > > > This change has caused regressions for many users and consumers. > > Playlist reloads only happen when a playlist doesn't indicate that > it > > has ended (via #EXT-X-ENDLIST), which means that the addition of > future > > segments is still expected. > > It is well possible that an HLS server is temporarily unable to > serve > > further segments but resumes after some time, either indicating a > > discontinuity or even by fully catching up. > > With a segment length of 3s, a max_reload value of 1000 corresponds > to > > a duration of 50 minutes which appears to be a reasonable default. Hi Steven, thanks for reviewing > I have no opinion about this, lgtm Neither do I. As this is a reversion, I meant to say that the original value wasn't irrational as it might have appeared when the change to 3 was made. Whether it's 100, 1000 or 10000 might be debatable, just 3 is way too low, so without any strong reason towards 100 or 10000, I think that going back to the original value makes the most sense. Thanks sw _______________________________________________ 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".
prev parent reply other threads:[~2025-02-07 2:40 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-01-19 8:52 softworkz 2025-01-19 9:27 ` Soft Works 2025-02-07 1:38 ` Soft Works 2025-02-07 2:24 ` Steven Liu 2025-02-07 2:39 ` Soft Works [this message]
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=DM8P223MB03650CD0C95361B41E3CEC92BAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=lingjiujianke@gmail.com \ /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