Hello, tsOffset is the initial timestamp when the camera module first
started streaming its data. It is intended to be used to manually align
multiple synchronized cameras.
If you've waited some time before starting the recording, that would
explain the 94 seconds time difference. If you want the initial
timestamp, then the timestamp of the first event recorded should do it.
All timestamps are in microseconds, starting from the Unix epoch, so
you can easily convert them back into real-time.
Hope this helps, have a nice day!
On Thu, 2020-04-16 at 03:12 -0700, Moritz Beck wrote:
> Hi,
>
> I'm using the dv-python package to process events. Is there any
> information in .aedat4 file included that gives me the initial
> timestamp the camera used? I've found this one but I'm not sure what
> it actually says:
>
> f._name_info_map['events']['tsOffset']
>
> It gives me some sort of timestamp (I assume in usec) but if I
> compare it with the first event that is triggered there is a time
> difference of over 94 seconds.
>
> Thanks for your help! Kind regards
>
> Moritz Beck
--
Luca Longinotti (llongi)
Software Engineer
iniVation AG -
https://inivation.com/
Zurich, Switzerland
Office:
+41 44 500 32 14
Support -
https://inivation.com/support/