Flag to encode system timestamp in Beast output #195
Conversation
|
What's the expected use of this new format? Have you considered using the Radarcape-style timestamp format (which represents nanoseconds since UTC midnight) rather than introducing a third format? I think this would need to be controlled by a negotiated option to avoid confusing existing software. |
xander-hirsch
force-pushed
the
beast_timestamp
branch
from
a3930f4
to
e3b3fa8
Compare
Beast clients can request for the message timestamps to be provided by the system clock as milliseconds since the epoch. This option is toggled by 't/T'. This option is client specific and off by default.
|
I've revised this pull request to incorporate your suggestion of a Beast client negotiated option, enabled by My motivation to provide system timestamps is to enable a much simpler record/replay solution. For example, a user can run I considered the Radarcape-style timestamp format; however, the date information is needed for the aforementioned use case. |
The
--beast-sys-timeflag allows a user to specify that Beast output messages should include the system timestamp (in milliseconds since the epoch) instead of an input device-specific timestamp. Providing this flag does not change the timestamp printed with each decoded message such as the example in issue #163.