summaryrefslogtreecommitdiff
path: root/libs/ultrahdr/jpegencoderhelper.cpp
diff options
context:
space:
mode:
author Harry Cutts <hcutts@google.com> 2023-11-24 14:34:03 +0000
committer Harry Cutts <hcutts@google.com> 2023-11-24 14:50:42 +0000
commit009262eaa26a15fb8c5442e3140dd18496c4c46e (patch)
treed5154c9d714f84359b3e82db69e9605cf1f9a4e8 /libs/ultrahdr/jpegencoderhelper.cpp
parent43881b0fa27a23422041337c89d95098a2d4b618 (diff)
evemu-record: add --timestamp-base option
This option allows recordings to be produced with the event timestamps relative to boot time (like those in dmesg), rather than the time of the first event received. Because evemu playback tools (e.g. uinput or evemu-play on desktop Linux) immediately play the first event they encounter and then subtract its timestamp from those of all following events, the timestamp base used should have no effect on playback [0]. Where timestamps relative to boot come in useful is when collating data from a recording with other logs. For example, the touchpad debugging logs report timestamps relative to boot time, so one could record touchpad input and those logs simultaneously, then automatically match up events in the evemu recording with the gestures recognized by the touchpad stack. [0]: In fact, FreeDesktop evemu used boot time as the timestamp base until version 1.2.0, so other timestamp bases have to be supported to maintain backwards compatibility. Bug: 302297266 Test: record events with --timestamp-base=boot, check recording replays correctly with uinput Test: check original behaviour is preserved when --timestamp-base isn't specified Change-Id: I89e9682bfc77267e0d5b2397c78ebfe4270e676f
Diffstat (limited to 'libs/ultrahdr/jpegencoderhelper.cpp')
0 files changed, 0 insertions, 0 deletions