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
{{ message }}
This repository has been archived by the owner on Jul 10, 2023. It is now read-only.
FrameTimestampIssue.zip
When the attached python code was run, we experienced 3 pairs of messages with the same timestamps. You can see these in the mqtt_logs.text at lines: 13/14, 21/22 and 25/26.
Wondering what is happening here, my understanding is that each MQTT message should come with unique and incremental timestamp. Is this an instance where both messages were generated close to each other so in the time resolution they fall in to the same ticker?
The text was updated successfully, but these errors were encountered:
We looked into this issue and identified incorrect timestamps in the media source that rippled through to MQTT. Closing as this is not a VA Serving issue.
FrameTimestampIssue.zip
When the attached python code was run, we experienced 3 pairs of messages with the same timestamps. You can see these in the mqtt_logs.text at lines: 13/14, 21/22 and 25/26.
Wondering what is happening here, my understanding is that each MQTT message should come with unique and incremental timestamp. Is this an instance where both messages were generated close to each other so in the time resolution they fall in to the same ticker?
The text was updated successfully, but these errors were encountered: