`timestamp_us` in `VideoFrame` being wrong

[TomCC7]

Hello, I'm trying to synchronize multiple video tracks for my application. However, I found that setting the timestamp_us field from the publisher side doesn't really affect the value from the subscriber side. Instead, on the subscriber side the timestamp is always a timestamp since the start of the subscriber computer. This behavior is really weird and I can't figure out where is the value assigned in the library (and no docs/issue talking about this).
Since in the definition of the VideoFrame the timestamp_us is described as when the frame was captured in microseconds, I think this is an unexpected behavior or a bug.

[TomCC7]

update on this issue: I tried using python sdk to subscribe to the same video track and the result is the same. So it seems to be not a rust sdk issue? Not sure where should I ask about this though.

[chenosaurus]

@TomCC7 that is correct, the timestamp_us field is not retained. We are discussing internally how to better support capture timestamp to be persisted thru the stream.