From: Steven Liu <lingjiujianke@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Liu Steven <lq@chinaffmpeg.org>,
FFmpeg user questions <ffmpeg-user@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg's HLS muxer's deprecation of the hls_wrap option
Date: Sat, 20 Jan 2024 23:42:24 +0800
Message-ID: <CADxeRwndYXFe1Ujid2E3XENk827pa5XgSnR4jRUO1GLj_f-gAA@mail.gmail.com> (raw)
In-Reply-To: <CAKKYfmE_LD1XxBgh3qLFH2gdqQWGfuRuHA=e9r8m2hHW=9TK1w@mail.gmail.com>
Dennis Mungai <dmngaie@gmail.com>于2024年1月20日 周六23:15写道:
> On Sat, 20 Jan 2024, 6:09 pm Steven Liu, <lingjiujianke@gmail.com> wrote:
>
> > Dennis Mungai <dmngaie@gmail.com>于2024年1月20日 周六21:02写道:
> >
> > > Hello,
> > >
> > > Is there a valid technical reason as to why FFmpeg's HLS muxer dropped
> > the
> > > hls_wrap option?
> >
> >
> > eg. three player playing the list and every fragment less or equal 1
> second
> > ,
> > 1. Player 1 from fragment1, fragment2
> > 2. Now Player 2 from fragment 1, fragment 2,
> > 3. Now Player 3 from fragment 1, Fragment2 and Player 1 playing fragment
> 3
> > 4. Network transport with player 3 get loss packet
> > 5. Player 1 playing new fragment 1, new fragment 2
> > 6. Player 2 playing fragment 3
> > 7. Player 3 blocking always because the fragments are flashing too fast.
> >
> > So the commit message said it is not friendly to downstream users.
> >
> > I have no more better way to fix it with ffmpeg, but I think that commit
> > can be revert if you want use hls_wrap.
> >
> >
> > > There are many cases where the hls_wrap option remains critical so as
> to
> > > preserve the set of output file names without increments. This
> > deprecation
> > > breaks that.
> > >
> > > For now, this behavior can be worked around by switching to the segment
> > > muxer and then setting the -segment_wrap option therein, but its' not
> an
> > > ideal solution.
> > >
> > > Kindly review this deprecation, with an appeal to revert the patchwork
> > that
> > > removed the hls_wrap option.
> > >
> > > Warm regards,
> > >
> > > Dennis.
> >
>
> Steven,
>
> The option should've been left intact, *but* with a warning on its
> implications on usage.
Dennis,
agreed with you, let me think about that.
> Multiple ffmpeg flags have similar edge case impacts
> when used improperly, eg -copyts and non monotonous timestamps, but they're
> not deprecated; they're still in place.
>
> >
Thanks
Steven
>
> _______________________________________________
> 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".
>
_______________________________________________
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:[~2024-01-20 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 13:01 Dennis Mungai
2024-01-20 15:09 ` Steven Liu
2024-01-20 15:14 ` Dennis Mungai
2024-01-20 15:42 ` Steven Liu [this message]
2024-01-20 16:41 ` Dennis Mungai
2024-01-22 10:09 ` Steven Liu
2024-01-22 10:20 ` Dennis Mungai
2024-01-22 11:03 ` Steven Liu
2024-01-22 11:32 ` Zhao Zhili
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=CADxeRwndYXFe1Ujid2E3XENk827pa5XgSnR4jRUO1GLj_f-gAA@mail.gmail.com \
--to=lingjiujianke@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=ffmpeg-user@ffmpeg.org \
--cc=lq@chinaffmpeg.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