[FFmpeg-trac] #5419(avformat:open): HLS EXT-X-DISCONTINUITY tag is not supported

[FFmpeg]

#5419: HLS EXT-X-DISCONTINUITY tag is not supported
------------------------------------+------------------------------------
             Reporter:  xyq204101   |                    Owner:  (none)
                 Type:  defect      |                   Status:  open
             Priority:  important   |                Component:  avformat
              Version:  git-master  |               Resolution:
             Keywords:  hls         |               Blocked By:
             Blocking:              |  Reproduced by developer:  1
Analyzed by developer:  1           |
------------------------------------+------------------------------------
Comment (by Elliot Lee):

 There are some relevant comments in https://github.com/jellyfin/jellyfin-
 ffmpeg/issues/57

 In particular:
 (a) "One of the major issues is that RFC-8216 is not fully supported in
 FFMPEG

 https://datatracker.ietf.org/doc/html/rfc8216

 #EXT-X-DISCONTINUITY is just one of the things from RFC-8216 that isn't
 supported properly in FFMPEG.
 #EXT-X-DISCONTINUITY-SEQUENCE is also not supported properly either.

 Just look through the RFC and you still see things missing from FFMPEG."
 (github user Protektor-Desura)

 (b) "Now, when it comes to supporting certain TV providers like Pluto,
 simply supporting discontinuity streams is not enough. This is because
 streams from providers like Pluto often break the HLS RFC spec in various
 ways, and a spec-compliant HLS demuxer would reject these streams as well.

 To illustrate, proper support for the #EXT-X-DISCONTINUITY tag requires
 the HLS stream to have an EXT-X-DISCONTINUITY-SEQUENCE header to mark
 which discontinuity sequence the current playlist is in. However, PlutoTV
 manifests may have inconsistent numbers between updates, with values
 jumping from 2 to 0 or 1. According to the RFC, a decreasing number is not
 allowed." (github user gnattu)

 So it seems there is more to untangling this whole ball of yarn than just
 applying the old patch.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/5419#comment:33>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker