Bug #2207
create timestamps in videosink are wrong
| Status: | New | Start date: | 03/20/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
Event Scope : /foo/ Id : 7BA80410-3F10-5FC0-A517-319754D5FC91 Sequence-Number: 126 Origin : 9257D36D-1076-4153-8E4D-D0E5AB6D393D Method : N/A Timestamps Create : 2015-03-17T11:50:49.350336+01:00 Send : 2015-03-20T15:52:15.707611+01:00 Receive: 2015-03-20T15:52:15.716142+01:00 Deliver: 2015-03-20T15:52:15.716151+01:00
History
#1 Updated by N. Köster over 7 years ago
and it is still haunting us today... -.-
issue phenotype:¶
'metaData': {'createTime': 1468224591.647322,
'deliverTime': 1469620743.624606,
'receiveTime': 1469620743.624573,
'sendTime': 1469620743.44114,
references:¶
point where the create time is set: https://code.cor-lab.de/projects/rsb-gstreamer/repository/revisions/master/entry/src/gst_rsb_video_sink.cpp#L318
point of conversion: https://code.cor-lab.de/projects/rsb-gstreamer/repository/revisions/master/entry/src/util.h#L52
#2 Updated by N. Köster over 7 years ago
actual line with issue:
"quickfix" is to do
event->mutableMetaData().setCreateTime((boost::uint64_t)0);
which will use the current timestamp. however this might be wrong for someone who needs an exact timestamp of an image...