[webrtc-encoded-transform] Should we add captureTimestamp senderCaptureTimeOffset to the RTCEncodedXXXFrameMetadata if abs-capture-time is used? (#225)

murillo128 has just created a new issue for https://github.com/w3c/webrtc-encoded-transform:

== Should we add captureTimestamp senderCaptureTimeOffset to the  RTCEncodedXXXFrameMetadata if abs-capture-time is used? ==
In the  https://w3c.github.io/webrtc-extensions/ we define the `captureTimestamp` and `senderCaptureTimeOffset` at contribution source level, however this information is available on a per frame level too.

I believe it would be interesting to be able to expose the same both values in the `RTCEncodedAudioFrameMetadata` and `RTCEncodedVideoFrameMetadata` when the abs capture time header extension is used.


Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/225 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 27 February 2024 13:53:47 UTC