From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v4] avformat/hls: Add option to retry failed segments for hls
Date: Thu, 20 Oct 2022 15:06:49 +0530
Message-ID: <22701501-6341-5c43-a1d7-d7440af02de6@gyani.pro> (raw)
In-Reply-To: <CADxeRwkH40yWOm+fTdAuGPw9asU4+B8GdBcZo4qVTm29yfdOvA@mail.gmail.com>
On 2022-10-20 03:03 pm, Steven Liu wrote:
> gnattu <gnattuoc@me.com> 于2022年10月19日周三 16:11写道:
>> Current HLS implementation simply skip a failed segment to catch up
>> the stream, but this is not optimal for some use cases like livestream
>> recording.
>> Add an option to retry a failed segment to ensure the output file is
>> a complete stream.
>>
>> Signed-off-by: gnattu <gnattuoc@me.com>
>> ---
>> v4 added documentation for the new seg_max_try option
>>
>> doc/demuxers.texi | 4 ++++
>> libavformat/hls.c | 15 ++++++++++++++-
>> 2 files changed, 18 insertions(+), 1 deletion(-)
>>
>> diff --git a/doc/demuxers.texi b/doc/demuxers.texi
>> index 2b6dd86c2a..3e09a0f14e 100644
>> --- a/doc/demuxers.texi
>> +++ b/doc/demuxers.texi
>> @@ -401,6 +401,10 @@ Use HTTP partial requests for downloading HTTP segments.
>>
>> @item seg_format_options
>> Set options for the demuxer of media segments using a list of key=value pairs separated by @code{:}.
>> +
>> +@item seg_max_retry
>> +Maximum number of times to reload a segment on error, useful when segment skip on network error is not desired.
>> +Default value is 0.
>> @end table
> ping Gyan help review document content :D
Looks ok.
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".
next prev parent reply other threads:[~2022-10-20 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 8:11 gnattu
2022-10-20 9:33 ` Steven Liu
2022-10-20 9:36 ` Gyan Doshi [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-12 12:10 gnattu
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=22701501-6341-5c43-a1d7-d7440af02de6@gyani.pro \
--to=ffmpeg@gyani.pro \
--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