Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/hls: Revert "reduce default max reload to 3"
Date: Wed, 26 Feb 2025 01:38:56 +0100
Message-ID: <20250226003856.GB4991@pb2> (raw)
In-Reply-To: <DM8P223MB03650CD0C95361B41E3CEC92BAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>


[-- Attachment #1.1: Type: text/plain, Size: 1932 bytes --]

Hi

On Fri, Feb 07, 2025 at 02:39:56AM +0000, Soft Works wrote:
> 
> 
> > -----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.

If 3 is too small and 1000 is too large then try the value in the middle
sqrt(3*1000) = ~50

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The worst form of inequality is to try to make unequal things equal.
-- Aristotle

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

      reply	other threads:[~2025-02-26  0:39 UTC|newest]

Thread overview: 6+ 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
2025-02-26  0:38     ` Michael Niedermayer [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=20250226003856.GB4991@pb2 \
    --to=michael@niedermayer.cc \
    --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