- From: vitaly-castLabs via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Jan 2023 05:08:00 +0000
- To: public-webrtc-logs@w3.org
I don't think it's true. What about frame_num and pic_order_cnt_lsb in the slice header? (paragraph 7.3.3 in 14496-10:2020(E)). But anyway it's not even relevant. What I'm looking for (maybe other people will find it useful too) is that every encoded frame (both audio and video) gets assigned a sequence number on the sending side and this sequence number is exposed on the receiver as well. Honestly I don't see any reason why this sequence number couldn't be taken care of WebRTC in a codec-agnostic way -- GitHub Notification of comment by vitaly-castLabs Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/166#issuecomment-1396447148 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 January 2023 05:08:01 UTC