[FFmpeg-trac] #1189(undetermined:closed): Seeking to timestamp 0 without AVSEEK_FLAG_BACKWARD results in seek to timestamp of 12

[FFmpeg]

#1189: Seeking to timestamp 0 without AVSEEK_FLAG_BACKWARD results in seek to
timestamp of 12
-------------------------------------+-------------------------------------
             Reporter:  mbradshaw    |                    Owner:
                 Type:  defect       |                   Status:  closed
             Priority:  normal       |                Component:
              Version:  git-master   |  undetermined
             Keywords:               |               Resolution:  invalid
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------
Changes (by reimar):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 As ffprobe -show_packets shows, the first frame has a (dts) time stamp of
 -1.
 Thus seeking to the first frame when seeking to timestamp 0 would be
 wrong.
 As far as I can tell FFmpeg behaves exactly as it should, and doesn't
 really have much choice in the matter.

 Note: I admit that it is up to discussion whether FFmpeg should rather be
 seeking by dts or pts, though by dts gives probably more logical/reliable
 results.
 Whether it should avoid creating files with negative dts yet another. I
 can't really comment much on either.
 It also looks like FFmpeg sets the start time to 0 and not -1, which while
 I believe is correct is rather confusing with that dts/pts mess.
 But even without that there are many, many file formats that almost never
 start with a time stamp of 0.

 Still, overall I do not believe there is any bug, even if the behaviour is
 maybe needlessly confusing or too badly documented, so there might be
 something for which you might want to open an enhancement request (or
 change this one to such if possible).

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1189#comment:1>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker