On 24-01-2021 12:40 am, Lynne wrote:
This is an RFC about the upcoming additions to the AVPacket structure
(whose size is still part of the ABI, so we need to plan for any changes).
The current RFC patch adds 3 fields:
- "void *opaque;" for the user to use as they wish, same as AVFrame.opaque
- "void *opaque_ref;" for more permanent and propagating user data, same
as AVFrame.opaque_ref
- "AVRational time_base;" which will be set to indicate the time base of
the packet's timestamps
Some devs (JEEB) wanted reception timestamps and original, overflowed
timestamps for MPEG-TS.
I'd be willing to add a reception timestamp as long as we add an additional
time_base field
and make it independent of the packet's pts field, since those timestamps are
usually on
highly precise system clock time bases, and reducing their precision would be
undesirable.
I'm not sure about overflowed original timestamps or how they would help.
Reception timestamps sounds useful.
Overflow timestamps may be useful, Right now, lavf rolls over timestamps
correctly only once, as the offset doesn't accommodate further loops.
Regards,
Gyan
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
