You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a few days of a stream the PTS timestamps will roll back to zero; we need to allow for this (the current logic does not allow PTS to go backwards).
One reason for the current explicit increase logic is to handle out-of-order packets, but I'm not sure if that is a real concern for the use case here, we can simply say to the end user that if you provide out of order packets, you may have out of order PTS times.
The text was updated successfully, but these errors were encountered:
The MPEG-TS pts field can roll over after a stream has been on for
a sufficiently long time (e.g. a week or so).
There was a failsafe built into the demuxer that would prevent PTS from
ever decreasing -- this was because normally PTS is not supposed to
decrease (outside of rollovers).
This change now assumes that the data stream will be passed in order in
order to maintain that PTS condition.
Issue #18
Task
Description
After a few days of a stream the PTS timestamps will roll back to zero; we need to allow for this (the current logic does not allow PTS to go backwards).
One reason for the current explicit increase logic is to handle out-of-order packets, but I'm not sure if that is a real concern for the use case here, we can simply say to the end user that if you provide out of order packets, you may have out of order PTS times.
The text was updated successfully, but these errors were encountered: