For multi-camera capture logs, define the camera identifier, capture session, frame sequence, timestamp, unit, clock source and event type. Record source sampling and receiver arrival separately. Give each restarted session a new identifier. Record disconnection, reconnection and the first frame after recovery to distinguish sequence resets from missing frames.

Distinguish packets and image frames

RTP sequence numbers advance per data packet. One video frame can span several packets. RTP timestamps represent media sampling times and use the applicable clock. The application can also log decoded frame numbers. For V4L2 capture, check buffer sequence numbers and timestamp flags against actual driver output.

Mark stream loss, backlogs and invalid frames

Identify the stage for each log entry: receipt, decoding, queue entry or later processing. For an unexplained sequence gap, compare packet sequences, decoding results and queue records. Log invalid frames, absent frames and deliberate frame skipping separately. Confirm the relationship between device clocks before comparing timestamps.

Keep samples around the fault

Save the same camera's logs from before and after a fault. Record the active configuration and version. In a retest, check whether logs identify the affected frames and stages during a pause, recovery or stream change.

Field definitions: RTP specification and kernel buffer documentation.