This message was deleted.
# helpdesk
s
This message was deleted.
The reason that I ask is it might help enable a frontend application to build out latency based features
p
if you’re fine with that you can use internal accessors to get the receiver via
remoteTrack.receiver
. However API stability is not guaranteed for internal APIs.
l
Thanks for the guidance. It looks like both the
timestamp
and the
rtpTimestamp
in the result of
getSynchronizationSources
are independent of the timestamp set on the
rtc.VideoFrame
. Does the
rtc.VideoFrame.timestamp_us
make its way to the clients of the LiveKit room, or is it only used for encoding/for the local participant's stream to the LiveKit room
Hey all, checking in again — is it possible to set the
ts
of an
rtc.VideoFrame
in the LiveKit python SDK to some meaningful value (e.g. the timestamp of the host machine when that frame was created, or the timestamp from when that frame was originally captured) and to access that same timestamp in the js/react SDK, for example the timestamp of the frame that is currently being shown in a
<video />
element?
Got some support for this offline. Looks like there's nothing in native WebRTC that exposes this to users, but it may be possible to leverage insertable streams to at least retrieve timestamps from the same RTP stream that includes the frames