[gareth-morgan-nv]

Summary

Puts camera video, glove and controller data on one PC timeline for recording, and shows end-to-end latency and fps on the page.

• One clock path. The PC (recorder) and the browser each run a four-timestamp exchange with the camera publisher over LiveKit data messages; the publisher answers with its monotonic clock. A mapping carries its uncertainty (half the round trip plus a drift allowance that grows with age at read time). A take ends on a missing, stale, jumped or over-budget mapping (EGOCAP_CLOCK_UNCERTAINTY_BUDGET_MS, default 5 ms, a policy choice).
• Recorded timestamps. Camera frames are recorded only on a monotonic basis: monotonic_us (the publisher's frame-ready time, the native sender's default) or capture_monotonic_us (sensor capture event). Tracking keeps the existing host poll timestamp. The take's timing attributes save the mapping evidence, the budget, what each camera time means (frame_ready / sensor_capture) and what each tracking time means.
• Page. Latency runs from the publisher's per-frame stamp (matched by RTP timestamp) to the expected display time; fps comes from presented frames.
• Native sender (camera_plugin_sensing). Answers the clock exchange; --timestamp-basis selects monotonic_us (default), capture_monotonic_us (converts the SIPL counter or Argus sensor timestamp through a 1 Hz anchor, failing the stream on an implausible value) or processing_unix_us. SENSING_ENCODER_TIMESTAMP_PROBE=1 logs encoder returned stamps.
• Agent-only plan notes are no longer checked in (agentPlans/ is git-ignored).

Limits

• Frame-ready time is later than the sensor's capture event; neither basis proves physical alignment between camera, glove and controllers.
• The encoder returns no submitted timestamp, so units are paired with captures by submission order; this can shift after an encoder-internal drop, so per-frame times are not hardware-qualified.
• Tracking device times (controller pose-evaluation time, Manus receipt/publishTime) are not carried into recordings; that needs changes outside egocap.

Validation

Run (mock stack, no hardware):

• pytest over tests/backend, tests/capture_server, tests/tools, tests/recording_service: 1181 passed, 100 skipped, 1 failed (tests/capture_server/test_gmsl_ipc.py::test_pipeline_serves_each_announced_frame_once_downscaled_as_jpeg, in code this PR does not touch; not checked against a clean checkout).
• Frontend: vitest 386 passed, tsc --noEmit clean.
• A take recorded through the local LiveKit server and the mock Orin emulator (fake clock offset, drift and pipeline delay) came out KEPT with the mapping evidence in its attributes. Shared-truth timeline tests read saved timestamp artifacts for both bases, with drop and clock-jump cases.
• pre-commit hooks (with SKIP=check-copyright-year) pass on the touched files; touched C++ was formatted with clang-format-14.

Not run: the native sender and Argus/SIPL paths were not built against the SDKs, nothing ran on an Orin, the Manus/controller paths were not exercised, and the page was not verified in a real browser by the author's tooling. The sensor-counter conversion (capture_monotonic_us) is unverified on hardware.

Stacked on #1429 (Argus), which stacks on #1428 (RearchBackend) and #1426 (FastLiveKit).

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: NVIDIA/IsaacCapture
• Branch: gmorgan/Argus
• File: .coderabbit.yaml
• Commit: e28d3bc
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Enterprise
• Run ID: f86c76ba-697f-4e46-8f87-42899030a870

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts