Voyager SDK timestamps explanation

Question

class FrameResult:image: Optional[types.Image] = Nonetensor: Optional[np.ndarray] = Nonemeta: Optional[AxMeta] = Nonestream_id: int = 0src_timestamp: int = 0sink_timestamp: int = 0render_timestamp: int = 0Could you explain when exactly these 3 timestamps are stamped? Our use case is we are trying to sync some telemetry samples with the exact moment the camera has recorded the frame. So it would be helpful to know what events trigger these timestamps.Thank you,

Spanner · Answer

Hi ​@mato, excellent question! Let’s look at them one at a time:src_timestamp: stamped when the frame first enters the Voyager pipeline (right after the source/decoder, as the stream ID is attached). It then travels with the frame.sink_timestamp: stamped when the fully processed result leaves the pipeline and is handed back to your application. The SDK's latency tracer reports sink - src as pipeline latency.render_timestamp: stamped when the frame is drawn by the display/render path (stays 0 with --no-display).Does that give you the info needed to sync things up? Let me know if not!

Sign up

Log in, or create an Axelera AI account

Login to the community

Log in, or create an Axelera AI account