- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Jun 2021 14:08:44 +0000
- To: public-webrtc-logs@w3.org
The bogeyman here is (of course) H.264 B-frames, which will cause frames with earlier timestamps to be sent (and received, if in order) after the (future) frames they refer to. The RTP sequence number is monotonically increasing in depacketization order; this argues for exposing the RTP sequence number and requiring that the frames are presented to the transform in RTP sequence number order. @guidou might have the reference. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/109#issuecomment-867667266 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 June 2021 14:08:52 UTC