#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):
MPEG's approach is rather naive, wouldn't you say? Each generation is
trying to simulate reality but to fit that simulation into (the existing)
frame architecture. It's a backwards approach. The next step is to create
I-MBs and P-MBs and B-MBs in an independent time domain and eliminate the
entire concept of frames. After that, to send just pixel motion
transforms. It reminds me of the techniques for modeling telltails on an
airplane wing.
FFmpeg would be smart to create a 12000x6000 display with pixels that
automatically refresh at around 10 or 12 refreshes per second right now,
and to then wrap that in a adaption layer that, on the outside, acts like
H.262 or H.264 or H.265 or H.266 etc.
But what do I know? I'm just a simple scientist. :-)
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11080#comment:63>
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".
