How a recording becomes a verdict

MF4 Log Analytics reads a dual-path controller recording, finds every power-up, and tells you which path started first, by how much, and why. Click a step, or play the walkthrough, then try the lab to see why clock-offset correction matters.

1 · Pipeline

Tip: use the arrow keys when a step is focused.

2 · Lab: why the clock offset matters

Each path logs on its own clock. Move the sliders and watch the raw timestamps, the offset-corrected result and the offset-free cross-check. Presets reproduce the demo recording.

3 · Impact: time saved

Defaults describe a long-duration test campaign: 10 recordings of about 4 GB, 57-60 start-up cycles each. Change the numbers to match your own project.

Estimates, not benchmarks. Manual time per cycle is the author's estimate; tool time was measured once on a 3.4 GB recording and is an upper bound. Recording time and the time spent reading results and deciding what to fix are not counted.