[FFmpeg-trac] #11055(avcodec:reopened): OGOP (Open GOP) in certain conditions may cause missing frames of decoding

[FFmpeg]

#11055: OGOP (Open GOP) in certain conditions may cause missing frames of decoding
-------------------------------------+-------------------------------------
             Reporter:  markfilipak  |                    Owner:  (none)
                 Type:  defect       |                   Status:  reopened
             Priority:  normal       |                Component:  avcodec
              Version:  git-master   |               Resolution:
             Keywords:  everything   |               Blocked By:
  OGOP                               |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by markfilipak):

 Replying to [comment:138 MasterQuestionable]:
 > ͏    Normalize priority.
 > ͏    I think this only influences not very much cases, mostly coined:
 > ͏    That only involves illy-produced videos.
 >
 > ͏    Doesn't merit high priority as one that could wreak general havoc.

 Please find something wrong with
 https://streams.videolan.org/ffmpeg/incoming/11055/Ticket_11055.m2ts. I'd
 dearly like to know what it is. If it is "illy-produced", show how is it
 "illy-produced". When "I think" becomes "We show", then I will believe it.

 I think this may be a far ranging bug that affects '-ss' and that provokes
 many of the "non-monotonous DTS" error messages that seem to appear out of
 nowhere when a trivial, non-timing, non-timestamp change is made to a
 transcode or to a remux. I confess that I write "I think" rather than "We
 think" because I've not yet gotten others on ffmpeg-user to look at
 Ticket_11055.m2ts and to take this issue seriously enough to join me.
 Certainly, no one else on ffmpeg-user has communicated that they've tested
 (or even watched) Ticket_11055.m2ts.

 This bug clearly wrecks '-vf showinfo' and '-show_frames' and makes them
 useless.

 According to an examination of the actual packets, only '-f framecrc'
 reports correctly.

 Please do not downgrade this bug without actual proof that is "illy-
 produced".
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11055#comment:140>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker