[FFmpeg-trac] #11080(undetermined:new): FFmpeg timestamps do not consistently agree with packet timestamps

[FFmpeg]

#11080: FFmpeg timestamps do not consistently agree with packet timestamps
-------------------------------------+-------------------------------------
             Reporter:  markfilipak  |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by markfilipak):

 Replying to [comment:13 Balling]:
 > You moved the first two B frames (their display) [refuted in the
 previous comment], so that made decoding of GOP impossible so it prints
 "co located POCs unavailable"

 Only 'ffprobe -show_frames' says "co located POCs unavailable". I think
 that's because the bug is affecting decoding. 'ffmpeg -f framecrc' does
 not decode, so it's unaffected by the bug. That's why 'ffmpeg -f framecrc'
 gives correct timestamps that match the actual packets.

 Look at the actual packets, please.

 Look, I know it is hard for you to accept that FFmpeg's timestamps are
 wrong. You're using FFmpeg functions to 'prove' things. I'm using the
 actual packets. That's physical evidence.

 You think the 2 B-frames are part of the right-side GOP. I think they're
 part of the left-side GOP that gets cut off. Let me ask you this: Why
 would dropping the 2 B-frames make any difference at all? Whether they're
 part of the left-side GOP or the right-side GOP, why would dropping them
 make a difference?

 I think this is a very old bug.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11080#comment:17>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker