[FFmpeg-trac] #6421(undetermined:new): PTS incorrectly fixed up to be negative

[FFmpeg]

#6421: PTS incorrectly fixed up to be negative
-------------------------------------+-------------------------------------
             Reporter:  sandersd     |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:               |                  Version:  git-
  undetermined                       |  master
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 Sample files available from:
   https://bugs.chromium.org/p/chromium/issues/detail?id=721451
   https://bugs.chromium.org/p/chromium/issues/detail?id=723537

 In the three cases reported above (7001A.mp4, MVI_5623.mp4, and
 nonFormattedMetaData.mp4), the first frame in presentation order is not
 the first frame in decode order. The metadata correctly records this.
 However, FFmpeg is reporting that the first frame in decode order is at
 time 0 (therefore the first frame in presentation order has a negative
 timestamp).

 Example (MVI_5623.mp4):
 {{{
 (edit offset is 40ms)

 # PTS PTS (after edit) ffprobe pts_time
 - --- ---------------- ----------------
 0 120  80                0
 1  40   0              -80
 2  80  40              -40
 3 240 200              120
 4 160 120               40
 5 200 160               80
 6 360 320              240
 7 280 240              160
 }}}

 (Tested with ffprobe at b946bd8ef2c7aeee09469a4901182a44f9b67189,
 2017-05-25)

 For comparison, ffprobe at release 2.8.11 reports the expected values:
 {{{
 # PTS PTS (after edit) ffprobe pts_time
 - --- ---------------- ----------------
 0 120  80               80
 1  40   0                0
 ...
 }}}

--
Ticket URL: <https://trac.ffmpeg.org/ticket/6421>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker