From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/hls: Revert "reduce default max reload to 3"
Date: Sun, 19 Jan 2025 09:27:43 +0000
Message-ID: <DM8P223MB0365C2ADF980E3B4E56FD13EBAE42@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <pull.51.ffstaging.FFmpeg.1737276758576.ffmpegagent@gmail.com>
> This change has caused regressions for many users and consumers.
See:
- https://www.reddit.com/r/mpv/comments/181yu2z/problem_streaming_radio/
- https://github.com/mpv-player/mpv/issues/13428
In my case:
Restreaming HLS to HLS. The source provides segments of 15s length, while
output is 3/6s segments. This causes segments in the output playlist to be
added "in waves", i.e. 5 segments are added (roughly) at the same time after
which no more segments are added for the next 15s. As the HLS demuxer reloads
the playlist in intervals of the segment length, it can easily happen that
will reload the playlist more than 3 times until a new segment appears in the
playlist.
Other example:
Since the HLS demuxer uses the duration of the last segment instead of the
target duration for the reload interval, it can also happen that one segment is
comparably short (which is perfectly valid) which can cause the 3 reloads to be
done even before a regular segment duration has passed.
Example cases for why 1000 is a reasonable default:
When receiving (e.g. for recording) from an HLS service which looses its
upstream connection for whatever reason (network outage, DDOS, etc.) it might
recover after some time, delivering all segments since the start of the situation.
A TV receiver streams via HLS and reception gets interrupted due to weather
conditions. The missed content is lost, but the HLS playlist can indicate a
discontinuity and resume serving segments.
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-01-19 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 8:52 softworkz
2025-01-19 9:27 ` 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=DM8P223MB0365C2ADF980E3B4E56FD13EBAE42@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.org \
--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