[FFmpeg-trac] #6305(undetermined:new): Negative AVIndexEntry::timestamp value
FFmpeg
trac at avcodec.org
Wed Apr 12 15:07:12 EEST 2017
#6305: Negative AVIndexEntry::timestamp value
-------------------------------------+-------------------------------------
Reporter: s0m3 | Owner:
Type: defect | Status: new
Priority: normal | Component:
Version: unspecified | undetermined
Keywords: | Resolution:
Blocking: | Blocked By:
Analyzed by developer: 0 | Reproduced by developer: 1
-------------------------------------+-------------------------------------
Comment (by s0m3):
I don't see how a (presentation) time stamp can be negative. Time can't be
negative.
Or maybe it means "too late" but first frame(s) cannot be late.
I know what correct timestamps are since (as you said) I created it.
But that's not the point. My goal is to know if I can trust AVIndex
entries for any file (where nb_index_entries != 0).
I found a sample file (no matter how I got it) where first entries are not
valid so it means I shouldn't use it (= not reliable).
But since decoding each frame to build an index myself can be very long,
I'd like ffmpeg to be fixed so that I can use AVIndex feature.
If media file is malformed, ffmpeg has to be fixed to generate a good one
AND to set nb_index_entries to 0 in this case.
If file is ok, ffmpeg has to be fixed so that each timestamp is valid and
not negative.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/6305#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list