From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org>
To: softworkz <ffmpegagent@gmail.com>,
"ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/hls: Revert "reduce default max reload to 3"
Date: Fri, 7 Feb 2025 01:38:48 +0000
Message-ID: <DM8P223MB0365DC4CC3C995A8EFD05423BAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <pull.51.ffstaging.FFmpeg.1737276758576.ffmpegagent@gmail.com>
> -----Original Message-----
> From: softworkz <ffmpegagent@gmail.com>
> Sent: Sunday, January 19, 2025 9:53 AM
> To: ffmpeg-devel@ffmpeg.org
> Cc: softworkz <softworkz@hotmail.com>; softworkz
> <softworkz@hotmail.com>
> Subject: [PATCH] avformat/hls: Revert "reduce default max reload to
> 3"
>
> 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.
> ---
> avformat/hls: Revert "reduce default max reload to 3"
>
> 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.
>
> Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-
> ffstaging-51%2Fsoftworkz%2Fsubmit_hls_reload-v1
> Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-
> ffstaging-51/softworkz/submit_hls_reload-v1
> Pull-Request: https://github.com/ffstaging/FFmpeg/pull/51
>
> libavformat/hls.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/hls.c b/libavformat/hls.c
> index 045741c3b4..426cf30f70 100644
> --- a/libavformat/hls.c
> +++ b/libavformat/hls.c
> @@ -2577,7 +2577,7 @@ static const AVOption hls_options[] = {
> {.str =
> "3gp,aac,avi,ac3,eac3,flac,mkv,m3u8,m4a,m4s,m4v,mpg,mov,mp2,mp3,mp4,m
> peg,mpegts,ogg,ogv,oga,ts,vob,wav"},
> INT_MIN, INT_MAX, FLAGS},
> {"max_reload", "Maximum number of times a insufficient list is
> attempted to be reloaded",
> - OFFSET(max_reload), AV_OPT_TYPE_INT, {.i64 = 3}, 0, INT_MAX,
> FLAGS},
> + OFFSET(max_reload), AV_OPT_TYPE_INT, {.i64 = 1000}, 0,
> INT_MAX, FLAGS},
> {"m3u8_hold_counters", "The maximum number of times to load m3u8
> when it refreshes without new segments",
> OFFSET(m3u8_hold_counters), AV_OPT_TYPE_INT, {.i64 = 1000},
> 0, INT_MAX, FLAGS},
> {"http_persistent", "Use persistent HTTP connections",
>
> base-commit: ced9fddec0e45e1ce1b3425a1fed66af971e934c
> --
> ffmpeg-codebot
PING - Maybe this wasn't recognizable as a patch due to the long text..
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".
next prev parent reply other threads:[~2025-02-07 1:39 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 [this message]
2025-02-07 2:24 ` Steven Liu
2025-02-07 2:39 ` Soft Works
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=DM8P223MB0365DC4CC3C995A8EFD05423BAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=ffmpegagent@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