#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):
This is for your amusement -- I'm not bitching...
Do you know what TPS means? Like 90000 TPS for MPEG and 1000 TPS for
matroska. It's "ticks per second" of course. The word "timebase" has no
meaning. "Ticks per second" has intrinsic meaning.
How about TPF? Like 90090/24 TPF or 90000/25 TPF. Ticks per frame.
PTS = N/TB/FPS becomes PTS = F*TPS/FPS = F*TPF :
(frames)*(ticks/sec)/(frames/sec) or better yet (frames)*(ticks/frame). If
I could get away with it, I would call "PTS", "picture tick stamp".
I taught the codesmiths who worked for me to use labels based on units
instead of abstract words. They told me that it did help them come up with
better, faster solutions and that it did help them to see bugs.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11080#comment:54>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".