Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Zhao Zhili <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: FFmpeg user questions <ffmpeg-user@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg's HLS muxer's deprecation of the hls_wrap option
Date: Mon, 22 Jan 2024 19:32:13 +0800
Message-ID: <tencent_7C688A03F968327E5AAFF63AA1C05DB6340A@qq.com> (raw)
In-Reply-To: <CAKKYfmEXxda2faL6XHMT-h0iHjVFwNV_J-4WuAK+5XByZbrp0A@mail.gmail.com>



> On Jan 22, 2024, at 18:20, Dennis Mungai <dmngaie@gmail.com> wrote:
> 
> On Mon, 22 Jan 2024 at 13:10, Steven Liu <lingjiujianke@gmail.com> wrote:
> 
>> Dennis Mungai <dmngaie@gmail.com> 于2024年1月21日周日 00:42写道：
>> 
>>>> 
>>> Perfect, and thanks for considering a revert of this deprecated feature.
>> 
>> Hi Dennis,
>> 
>> Need more talk, Why don't try to use hls_flags
>> +delete_segments+append_list. ?
>> 
>> 
>> Thanks
>> Steven
>> 
> 
> As stated earlier, even with these flags, we cannot replicate the advantage
> of the deprecated -hls_wrap whereby the segment names remain constant.
> append_list only omits the #EXT-EXT-ENDLIST tag.

The hls_wrap conflicts with current HLS specification, which add the restriction
at 2014. The specification explicitly says "EXT-X-MEDIA-SEQUENCE tag MUST
NOT decrease or wrap". So hls_wrap can’t be reverted.

Try what Steven suggests, or figure out a better idea than revert hls_wrap.

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

      parent reply	other threads:[~2024-01-22 11:32 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
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 [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=tencent_7C688A03F968327E5AAFF63AA1C05DB6340A@qq.com \
    --to=quinkblack@foxmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=ffmpeg-user@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