- From: nisse-work via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Jun 2022 08:21:41 +0000
- To: public-webrtc-logs@w3.org
Confusing indeed. Seems this was discussed previously on https://github.com/w3c/webrtc-encoded-transform/pull/116. Exposing capture time should be reasonably easy on the send side (prototype cl to do that for video: https://webrtc-review.googlesource.com/c/src/+/265403). I don't really understand the issues in getting that kind of timestamp on the receive side. If it can't easily be set to useful value on receive side, making it optional would be an improvement for use cases I have in mind. -- GitHub Notification of comment by nisse-work Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/135#issuecomment-1150821221 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 June 2022 08:21:42 UTC