Fix minor typos in MediaPipe synchronization description.
PiperOrigin-RevId: 515362264
This commit is contained in:
parent
39e2c8351f
commit
2c64421471
|
@ -113,14 +113,14 @@ Warning: On the other hand, it is not guaranteed that an input packet will
|
|||
always be available for all streams.
|
||||
|
||||
To explain how it works, we need to introduce the definition of a settled
|
||||
timestamp. We say that a timestamp in a stream is *settled* if it lower than the
|
||||
timestamp bound. In other words, a timestamp is settled for a stream once the
|
||||
state of the input at that timestamp is irrevocably known: either there is a
|
||||
timestamp. We say that a timestamp in a stream is *settled* if it is lower than
|
||||
the timestamp bound. In other words, a timestamp is settled for a stream once
|
||||
the state of the input at that timestamp is irrevocably known: either there is a
|
||||
packet, or there is the certainty that a packet with that timestamp will not
|
||||
arrive.
|
||||
|
||||
Note: For this reason, MediaPipe also allows a stream producer to explicitly
|
||||
advance the timestamp bound farther that what the last packet implies, i.e. to
|
||||
advance the timestamp bound farther than what the last packet implies, i.e. to
|
||||
provide a tighter bound. This can allow the downstream nodes to settle their
|
||||
inputs sooner.
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user